GitHub verdict · build Solution request

Playwright plugin for interactive debugging on failure

Built for QA engineers and test automation developers using Playwright who spend significant time debugging flaky or failing tests.

“In TestCafe, there's a simple `--debug-on-fail` command line flag that automatically pauses the test if it fails, so you can troubleshoot and debug it. It is si…”

The receipts — real demand

“In TestCafe, there's a simple `--debug-on-fail` command line flag that automatically pauses the test if it fails, so you can troubleshoot and debug it. It is singularly one of the most used and useful command line flags for me in TestCafe, I run it with at least 95% of my test runs. It doesn't seem that Playwright has this pause on fail option, making troubleshooting test failures a big pain. Trying to pinpoint …”
GitHub · view original →

Full dossier

Unlock the full dossier — free

Every corroborating quote, the source receipts, and the community echo. One email, no payment.

6.2 / 10 · demand score
Pain 6
Willingness to pay 1
Feasibility 7
Specificity 7
Audience 6
Competition 2

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.

The market

QA engineers and test automation developers using Playwright spend significant time debugging flaky tests and want a native pause-on-fail feature like TestCafe offers. No search volume data; confirm whether Playwright adoption is high enough in your target orgs to justify a plugin vs. a TestCafe migration.

Competition & the opening

Open field · 2/10

TestCafe has the `--debug-on-fail` flag built-in; Cypress offers interactive debugging; Playwright's own inspector exists but is less integrated. The 2/10 competition score indicates Playwright users have voiced this gap but few have filled it, creating real daylight for a focused plugin.

What's hard to build

Playwright's architecture requires hooking into test execution at the right moment and pausing gracefully without hanging the test runner; you'll need deep familiarity with Playwright internals and careful handling of async context. The 7/10 feasibility score reflects solid technical effort but bounded scope—this is a plugin, not a full platform.

Why now

Playwright dominates E2E testing but lacks TestCafe's ergonomic debugging UX that users are actively missing.

How you'd monetize

Free open-source Playwright plugin