...
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. 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.
...
The DTP filter must be configured to receive Run Configurations that contain test and coverage data. See Associating Coverage Images with Filters. You can confirm that the filter and build meet these requirements by looking at the Build Administration widget:.
| Anchor | ||||
|---|---|---|---|---|
|
...
The assets that enable Test Impact Analysis are installed as part of the the Process Intelligence Pack installation. Refer to the Process Intelligence Pack installation instructions for details. After installing the flow, deploy the report to your DTP environment.
- If you have not already done so, install the Process Intelligence Pack.
- Open Extension Designer and click the Services tab.
- Expand the Process Intelligence Engine service category. You can deploy assets under any service category you wish, but we recommend using the Process Intelligence Engine category to match how Parasoft categorizes the assets. You can also click Add Category to create your own service category (see Working with Services for additional information).
- You can deploy the artifact to an existing service or add a new service. The number of artifacts deployed to a service affects the overall performance. See Extension Designer Best Practices for additional information. Choose an existing service and continue to step 6 or click Add Service.
- Specify a name for the service and click Confirm.
- The tabbed interface helps you keep artifacts organized within the service. Organizing your artifacts across one or more tabs does not affect the performance of the system. Click on a tab (or click the + button icon to add a new tab) and choose Import from the vertical ellipses menu.
- Choose Local> Flows> Workflows> Process Intelligence> Local > Flows > Workflows > Process Intelligence > Test Impact Analysis and click Import.
- Click anywhere in the open area to drop the the artifact into the service.
- Click Deploy to finish deploying the artifact to your DTP environment.
- Return to DTP and refresh your dashboard. You will now be able to add the related widgets.
...
Because you can run the Test Impact Analysis slice over extended periods of time, the slice includes a caching mechanism to speed up multiple requests for the same data. When data is requested, the slice first determines if the data is already computed and cached. If the cache exists, the data is returned directly, and the lengthy computation is skipped. The cache is cleared and recomputed at runtime, however, under the following conditions:
- no No data is cached.
- the The cached data is associated with a different build combination.
additional Additional coverage data has been reported to the build combination.
There is one cache per filter and combination of baseline and target build.
...
| Title | You can change the default title of the widget. |
|---|---|
| Filter | Choose a filter from the drop-down menu. A filter is a collection of test execution and code analysis metadata configurations that enables DTP to aggregate, subset, and analyze specific swathes of data. |
| Period | Choose a range of time or number of builds to set as the scope. |
| Baseline Build | The build that you want to compare to the target build. |
| Target Build | The build you want to analyze; typically. Typically, this is the latest build. |
| Coverage Image | Coverage images are identifiers for the coverage data associated with a test run. The filter must be set to the correct coverage image to present information. |
...
You can perform the following actions in this report:
- Click on a link in the File Name, Pass, Fail, or Incomplete column opens the the Test Explorer view with the latest build ID.
- Click on a link in the Retest column opens the the Test Explorer with the baseline build ID.
...