...
In order to generate accurate results, the test case information is merged across two builds. Baseline and Target build ID are configured through drop-down menus when the widget is created. Both builds require The Baseline build requires coverage and dynamic analysis data and the Target Build requires coverage data for the widget to render properly. If the Target Build has test run data, it also needs to have test details. Without test details, target test results can't be displayed in the widget or report and the proper tests in the baseline won't have their "Action" fields set to "Retest" in the Test Explorer.
| Warning | ||
|---|---|---|
| ||
Coverage data stored in previous versions of DTP (5.3.2 and older) cannot be used to calculate testing metrics used in this extension. You will need to send a new test and coverage report to DTP server and set the build containing the new reports as the baseline when configuring the widget. You can resubmit a previous build report to the data collector to populate the data. Once the data is in DTP, make sure to archive the build so that it won't be removed during normal database clean up (see Locking and Archiving Builds). |
...
- no data is cached
- the cached data is associated with a different build combination
additional
analysiscoverage data has been reported to the build combination
Note Parasoft analysis tools upload test report (report.xml) before the coverage report (coverage.xml). If you are manually uploading reports, make sure to upload the test report before the coverage report. If the last report you upload is a test report, the cache will not be recomputed properly.
There is one cache per filter and combination of baseline and target build.
...