Identify the cause of a broken test easily
Automatic identification of the root cause of broken tests, 4/2025
One view with all information to inspect what went wrong with a broken test, 4/2025
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, 4/2025
Advanced test debuggin options to open playwright trace recording and run the test locally, 4/2025
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, 12/2024
Option to fix your broken test, 4/2025