Root Cause Analysis was introduced in an earlier release of Testimony (v2.30). Further changes to the useability of the report and how it is executed have been delivered in v2.50.

The confirmed process is the following:

  1. Build Execution Queue
  2. Perform Playback (double playback)
  3. Trigger Deep Impact Link Creation in target for “failed” objects (or other statuses)
    Trigger from central system in UI in Testimony
    Perform to N levels deep (see statistics on next slide)
    Monitor and trigger further levels (if time permits)
  4. Create “Build List” from central system representing “changes under test” in target
  5. Trigger Root Cause Analysis in central finding links from failed objects (or defects) to transport requests (in the build list)
  6. View RCA results at defect level – filter for “RCA Flag” in defect results screen

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment