Red signals the test has failed. This is due to 3 reasons:

​
1. You have a bug in your app

We will pinpoint you to the exact moment where it broke. We will pre-classify a possible root cause of the failure, give you timeline of what happended during test execution and the ability to compare with previous successful runs. For an even more precise debugging, you can launch the trace viewer or our open source Debugtopus to use locally on your machine.
Timeline of the test run to swipe through pinpointing where the test broke 04/2025

Timeline of the test run to swipe through pinpointing where the test broke 04/2025

​
2. The test is broken

End-to-end tests tend to break when the app changes. This is not just annoying, but a major time investment. With the help of our test inspection and debugging tools, you’ll easily detect the cuplprit and the Agent will even suggest an auto-fix of the broken test.
Example of an auto-fix suggestion of a broken test,

Example of an auto-fix suggestion of a broken test, 3/2025

​
3. The test is flaky

Flaky tests produce different results when running the exact same test case. We are deploying multiple strategies to fight flakiness, but it can’t be prevented 100% of the time just yet.