It's important to distinguish between the Pareto chart "Step that caused UUT to fail" in the Test Reports module and failed steps in general. This article explains the difference and the purpose of each.
Purpose of the Pareto Chart: "Step that caused UUT to fail"
A UUT report can have multiple failed steps (Failed, Error, Terminated), some critical and others not. The chart titled "Step that caused UUT to fail" in Test Reports is designed to capture the one failed step that caused a UUT report to fail (Failed, Error, Terminated). It does so for all UUT reports in the current search, compiling them into a Pareto chart.
The chart helps users quickly identify which steps are most often responsible for causing UUTs to fail, offering insights into the most significant issues without needing to delve into the details.
Failed steps in general
To view all failed steps, use the Test Step Analysis module. It provides a comprehensive overview of all test steps in a sequence, detailing all failed steps, not just those that caused a UUT to fail.
As seen in the screenshot below:
- Failed/Error/Terminated #: Shows the total number of times each step failed.
- Caused UUT Failed/Error/Terminated #: Indicates how many times each step caused the UUT to Fail, Error, or Terminate. This column is the basis for the Pareto chart.
Why differentiate?
Distinguishing the specific step causing the UUT to fail helps quickly identify areas for improvement. Consider these examples to understand the value of not including all failed steps in the Pareto chart:
- Static Steps: A step like turning on a power supply might fail a few times before succeeding.
- Loops: A step might fail repeatedly before eventually passing.
- Allowed Failures: Some steps may be configured to allow to fail without affecting the overall UUT status.
- Continued Testing: A test might continue to completion even after a failure, recording more failed steps that don’t necessarily cause the UUT to fail.
In conclusion
While the Pareto chart is useful for quickly identifying critical failure points, it does not provide the full picture. For full analysis, using Test Step Analysis is recommended. This module allows you to view all steps in a test sequence, the number of failures for each step, and which failures caused the UUT to fail.
See also:
Comments
0 comments
Please sign in to leave a comment.