The Test Audit App is provided with a set of Most-at-risk objects obtained from the Smart Impact App, and performs an audit of the objects, retrieving usage data for them from the QA and Production systems. Optionally, the Most-at-risk tokens are used to retrieve matching test executions from the specified Tosca, qTest or ALM Test Repository, and the App reports the run status of each test execution.
A user with LiveCompare Editor privileges must prepare this App by making sure that daily usage audit (DUA) data is available for the ‘QA System’ RFC Destination, and that performance history data is available for the ‘PRD System’ RFC Destination. See the ‘Prerequisites’ section below for details.
Before running the Test Audit App for the first time, you will need to make sure that DUA data is available on the RFC Destination selected for the QA system. Select the RFC Destination in the LiveCompare hierarchy and click the DUA tab. Set the number of months of data to retrieve, then click ‘Update Data’.
You should also make sure that performance history data is available on the RFC Destination selected for the production (PRD) system. Select the RFC Destination in the LiveCompare hierarchy and click the PHD tab. Select the source for performance history data, and if necessary the number of months of data to retrieve, then click ‘Update Data’.
Running the App
To run the Test Audit App, select the App from the Apps screen and create an App variant. Complete the variant screen as follows:
- Set the ‘Start Date’ control to the start date for which daily usage audit data is to be retrieved from the QA system.
- Set the ‘End Date’ control to the end date for which daily usage audit data is to be retrieved from the QA system.
- Set the ‘QA System’ field to the RFC Destination for your QA system, from which daily usage audit data has been retrieved.
- Set the ‘PRD System’ field to the RFC Destination for the Performance History system used when running the Smart Impact App.
- Edit the ‘Tokens’ table to provide a list of Most-at-risk tokens. The tokens may be obtained from the Impacted Objects Excel spreadsheet generated by the Smart Impact App.
- Set the ‘Search test executions?’ switch to specify whether the Test Repository will be searched to find test executions matching the Most-at-risk objects.
- If required, set the ‘Test Repository’ field to the Tosca, qTest or ALM Test Repository to be searched for matching test executions. Choose --Not Selected-- if required to clear your selection.
- Edit the ‘Test Search Paths’ string list to provide a list of test execution paths to be searched, for example (for Tosca Test Repositories), ‘/Root/Test Set Folder/Test Cases’. Each path and all its descendants are searched. If this parameter is not set, all repository paths will be searched to find matching test executions.
Click ‘Run’. When the variant has completed, its results may be accessed from the App Cockpit screen.
The Test Audit App generates a Dashboard report which includes a treemap showing the tokens that were matched in the specified Repository, and the status of their associated tests, either ‘Not Run, ‘Failed’ or ‘Passed’. The tokens are grouped by Application Area. It also includes links to the following reports.
This report includes the following spreadsheets:
This spreadsheet displays the charts shown in the Dashboard report.
This spreadsheet provides help for each of the spreadsheet reports.
Test Audit Details
This spreadsheet displays usage data for the Most-at-risk objects, obtained from the QA and production systems. The BUSINESS_CRITICAL column is populated using the Business Critical Objects External Data Source.
Test Execution Details
This spreadsheet displays the ID, path and run status for tests stored in test executions in the specified Test Repository. The spreadsheet is populated if the App’s ‘Search test executions?’ switch is set to ‘Yes’.
This report includes the following charts:
- The Test Audit summary pie chart summarizes the Most-at-risk objects, indicating whether they have been run on the QA system according to the retrieved daily usage audit data.
- The Test Execution Summary column chart summarizes the test instances in the specified Test Repository according to their run status. This chart is displayed if the App’s ‘Search test executions?’ switch is set to ‘Yes’.
Dashboard tiles indicate the name of the QA system, the range of dates for which performance history data was found, whether test labs were searched, and the name of the specified Test Repository. It also includes links to the Test Audit Excel Report described above, and the Analysis Input Data report described below.
This Excel report contains a copy of the input parameters used to produce the App’s Dashboard report. The value of each input parameter is stored in a separate worksheet, which is named after the parameter whose value it contains.