Test Impact Radar (0043) analysis can be used to highlight what top level SAP objects (e.g. Transactions, programs, etc.) are impacted by the selected transport(s). For example, if a database table structure was changed it could be used to identify all transactions and programs that use that table to help target testing effort.
It can also indicate what Test Scripts are impacted by the changes in the transports if these have been uploaded into ActiveControl. I.e. identify what test scripts should be executed at a minimum as a result of the changes contained in the transports.
It can also be linked to Production Usage Statistics to provide a more focussed indicator of impacted objects, and also optionally used to identify objects that are not mentioned in an organisations library of Test Scripts.
Note that there is some pre-requisite Object Linkage setup that needs to be performed for the Test Impact Radar analysis check to run correctly. Please refer to ‘Test Impact Radar’ section of this Administration Guide for details of this setup.
Parameters
| Parameter | Description |
|---|---|
| CHECK_LINKS | Check if the link creation is up to date. |
| IS_NEW_DI_LINKS | Should always be X (Yes). |
| MAX_LEVEL | Maximum recursion level for analyser (Default = 10). |
| MAX_OBJ_TIME | Maximum time to analyse an object (Default = 60 seconds). |
| NOT_IN_TESTSCRIPT | Optional. Can be used if the Analyser is required to report on analysed objects that are not covered by existing test scripts. Please refer to this Knowledge Article for further information. |
| TARGET | Target ID where the dependencies will be checked. |
| USAGE_PRIORITY | Optional. Can be used if Analyser is required to take Production Usage Statistics into account. Please refer to this Knowledge Article for further information. |
| USAGE_PRIORITY_SOURCE | Optional. Can be used if Analyser is required to take Production Usage Statistics into account. Please refer to this Knowledge Article for further information. |
Post your comment on this topic.