Setup Process

In order to fully setup and configure RCA for use, please use the following set of steps:

Installation of Active Control

Whilst there are no direct technical dependencies between AC and Testimony, the RCA functionality will not function correctly without AC installed. It does not require any configuration, it simply needs to exist as an installed add-on to the central and target systems.

Deep Impact linkage creation

After AC has been installed into the target system, the linkages program must be run within this system. This may be done prior to the playback. It could even be done in the source system first and then be copied over to the target system. Do not forget you’ll need Diffuser license keys to run the linkage program which will be provided during implementation of Testimony.

Root Cause Analysis parameter

This parameter must be activated in the general parameters section in the central system. Without it activated, you will not see the following:

• The tab “Root Cause” in the display of a defect
• The button in “Playback Overview” to run “Root cause analysis”
• The tab in “Playback Overview” that shows you the results of overall RCA run

Build list creation

A build list represents the “release” or set of changes that are being regression tested with Testimony. It can be automatically populated from the transports deployed to the target system since the recording started. The build list contains the list of objects that have been changed upon each transport request.

!If you do not see the “Build Lists” option in the Testimony “Execution” menu, then you may not be in the right User Interface Profile. In v2.21, this menu item is available to those users in the “Test Engineer” delivered UI profile.

Run Defect proposal

You should run the defect proposal process after a playback is finished in order to generate the defects at an aggregate level to the failures. RCA related data can be viewed as an overall outcome once it has been run, however, users who are routed defects should be able to view the underlying root causes of those defects when they are assigned and analyzed.

Run Root Cause Analysis

Assuming all of the previous steps have been successfully processed, then it is finally time to process all defects and attempt to find the underlying changes that may have caused those failed objects.

Review Output

There are three ways in which to see the results of running the root cause analysis.

1. Review overall root cause anlaysis output – This can be navtigated to via the Result Overview and the “Root Cause” tab for the selected queue. All data that has been derived by Root Cause Analysis can be seen within this area so you’ll know whether underlying root causes have been identified or not.
2. Within the defect management diplay – If you navigate to the defect management grid, you will see all defects that have been generated by the defect proposal run. A new flag has been added (also available as a filter option) to show whether a given defect has one or more related root causes.
3. Within a particular defect – If you select a particular defect that has one or more root causes identified for it, then these will be visible in the “Root Cause” tab for that defect. If no root causes are found then this grid will be empty (or invisible).