CTAL-TAE · Question #76
An automated test case that should always pass, sometimes passes, and sometimes fails intermittently (non-deterministic behavior) when executed in the same test environment, even if no code (i.e…
The correct answer is B. Determining the specified root cause may require, in addition to the TAE, the support of others. Intermittent (flaky) test failures can have multiple possible causes (e.g., timing issues, environment instability, resource contention, or hidden defects). Since no code has changed, identifying the true root cause often requires collaboration between the TAE, developers, and…
Question
An automated test case that should always pass, sometimes passes, and sometimes fails intermittently (non-deterministic behavior) when executed in the same test environment, even if no code (i.e., SUT code, or the test automation code) has been changed. Which of the following statements about the root cause of this non-deterministic behavior is TRUE?
Options
- AThe specified root cause is a race condition that can be identified by also analyzing the log files of
- BDetermining the specified root cause may require, in addition to the TAE, the support of others
- CThe specified root cause must be in the instability of the test environment, since no code has
- DDetermining the specified root cause is certainly easier than if the automated test always fails
How the community answered
(45 responses)- A11% (5)
- B64% (29)
- C20% (9)
- D4% (2)
Explanation
Intermittent (flaky) test failures can have multiple possible causes (e.g., timing issues, environment instability, resource contention, or hidden defects). Since no code has changed, identifying the true root cause often requires collaboration between the TAE, developers, and system engineers. This ensures that all potential layers (test code, SUT, infrastructure) are properly analyzed.
Topics
Community Discussion
No community discussion yet for this question.