A Node.js powered end-to-end testing framework for web and native mobile applications.
Free plan
No reader votes yet, so reviews and saves set the order. 6 have a free way in.
Test debugging means finding out why a software test failed and fixing the cause. These tools help you inspect problems, repeat tests, and check the result. For example, you can trace a broken sign-in test or find why a button behaves differently in another browser. This helps you catch issues before users do.
Missing a tool?
No reader votes yet, so reviews and saves set the order. Your vote moves a tool up this list. Press it on any row. No account needed.
A Node.js powered end-to-end testing framework for web and native mobile applications.
Free plan
A JavaScript testing framework for writing, running, and debugging browser-based tests with AI-powered features.
Free plan
Custom pricing
An AI-accelerated software testing platform for automated and manual testing across web, mobile, API, and desktop applications.
Free plan
from $1000 per year
An end-to-end testing framework for modern web applications supporting multiple browsers and platforms.
Free plan
An open source frontend workshop for building, testing, and documenting UI components in isolation.
Free plan
A next-generation browser and mobile automation test framework for Node.js.
Free plan
Showing 1 to 6 of 6
Know one that belongs on this list?
Which Test Debugging tool do you use, and why?
Join the discussion
Takes a minute. No account needed.
+10 points a postStart with a tool from the list:
Your choice depends on what you test and how your team already works. Start with the kind of problem you need to investigate most often, then check which option connects with your current setup.
Web teams often combine debugging with browser automation and end-to-end testing, so they can follow a full user journey and find where it breaks.
A broader setup may cover APIs and complete user journeys in one place through software testing automation.
Component-focused work often pairs debugging with regression testing, helping you spot when a recent change affects an existing interface.
It helps you investigate failed software tests, find the cause, make a fix, and run the test again.
Nightwatch.js, Cypress, Playwright, and WebdriverIO are used for cross-browser testing.
Nightwatch.js and Katalon are used for API testing.