...
| Anchor | ||||
|---|---|---|---|---|
|
- Parasoft DTP and Extension Designer
- Test and coverage data from the following Parasoft tools are supported:
- C/C++test Standard, dotTEST, and Jtest 10.4.3 or later.
- C/C++test Professional 10.4.3 or later.
- SOAtest 9.10.7 or later.
- The following metrics should be enabled in the code analysis tool (see Metrics Tab for information on enabling metrics and for metrics documentation) for the DTP filter:
- METRIC.MI (Maintainability Index)
- METRIC.NOLLOCIF (Number of Logical Lines in Files)
- METRIC.NOMIT (Number of Methods in Types)
- The DTP filter must be configured with Run Configurations that contain static analysis, metrics, test, and coverage data. If the builds configured in this widget do not have static analysis, metrics, test, and coverage data, the Risky Code Changes logic will not function. See Associating Coverage Images with Filters.
...
Because you can run the Risky Code Changes 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 for a filter, 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 on the fly, however, if the data is not cached, if the cached data is for a different build combination, or if more analysis data has been reported to the build combination, then the cache is cleared and recomputed on the fly. There is a maximum of one cache per filter and combination of baseline and target build.
| Anchor | ||||
|---|---|---|---|---|
|
Because the slice does not automatically remove cached data, the cache can grow as more filters are introduced. To help you clear out old cache data, the slice provides a way to delete all cached calculations from the PIE database. This flow cleans all cached calculations. The cache also clears at 00:00 every day. You can configure the auto cache clearing setting by editing the Clean Cache inject node.
...
Verify that the filter has a coverage image associated with it (see Associating Coverage Images with Filters) and that the correct coverage image was selected when you added the widget (see Widget Configuration).
If an error persists after you have addressed the root cause, you may need to clear the cache.