Solved
Managing Failures - New vs. Expected/Known Issues
Our test suites run on a schedule in multiple environments, using test runner to run tests using tags to run test cases across multiple test suites. We're struggling to monitor all our test executi...
Hi mnwill117
Use ReadyAPI’s native fail/pass as the raw result, and handle known issue vs new failure in a separate reporting layer.
- A good approach is a step-level registry keyed by test case, step, environment, and issue ID, so known failures are tagged after execution.
- Avoid changing failed steps to “unknown,” because that hides real failures and weakens trends over time.
Instead, keep execution status unchanged and suppress or route alerts based on whether the failure matches a tracked issue.
For your setup, this is usually the cleanest way to get a warning-like view without altering ReadyAPI’s core result model.
Hope this helps !!
