No need to sift through a red wall of broken tests. Figuring out what went wrong can be a huge time investment, especially when your test suite grows. We will help you make you identify the reason for the failure really fast.

​
We have classified the root cause of the broken test

Octomind analyzes the root cause of failed tests automatically. Slow page loading, potential bug, failed test dependency … we will do the first step you indentify why the test failed. And we will give you the tools to investigate further.
Automatic identification of the root cause of broken tests

Automatic identification of the root cause of broken tests, 4/2025

​
Inspect what happened in one single place

To save you the hassle of jumping mental context back and forth to figure out what went wrong, we have packed everything into one view. One place to oversee the test run timeline, root cause, agent commentary, compare test runs, check error log and more.
One view with all information to inspect what went wrong with a broken test

One view with all information to inspect what went wrong with a broken test, 4/2025

​
Compare the broken test with previous successful test runs

It’s possible you have many tests to manage and you’re not sure where that failed step was supposed to go. Maybe you didn’t even create the test and don’t have the context. Click on compare runs in the upper right corner and swipe through the last successful runs and their timeline history.
test run history to compare failed and successful test runs to investigate the test context

test run history to compare failed and successful test runs to investigate the test context, 4/2025

​
Advanced test debugging

If you need more detailed insight into the test failure you can:
  • launch the Playwright Trace Viewer to investigate the playwright traces step by step
  • run the test locally with our open source Debugtopus. It is an additional help that allows you to set breakpoints and step through the code.
Advanced test debuggin options to open playwright trace recording and run the test locally

Advanced test debuggin options to open playwright trace recording and run the test locally, 4/2025

​
Playwright Trace Viewer

In the advanced section of a test result, click on the respective Playwright trace to access to the Playwright Trace Viewer for an advanced visual debugging UI. A GUI tool will open, with a granular timeline complete and detailed diagnostic information such as actions (clicks, navigation), events, console messages, network requests, and more that were generated during a test run.
Screenshot of Playwright Trace Viewer with failed steps

Screenshot of Playwright Trace Viewer with failed steps, 12/2024

Developers will be familiar with the tabbed interface at the bottom of the screen which functions similarly to in-browser developer tools.

​
What to do next? How to I fix the test?

If you identified a broken test - a change in the app caused the test failure (e.g. a new build has broken the test locator), it means it’s fixable. There are several options how to fix it:
Options to fix your broken test

Option to fix your broken test, 4/2025