5 of 5 free conversions left. Sign in for unlimited use.
PlayRight Failure Analyzer
Paste the error and call log of a failed Playwright test (Playwright Test or pytest-playwright). A rule engine with visible weights decides whether the cause looks like a locator, timing, data, app-bug or environment problem, shows the rules that fired as evidence and suggests fixes with code. It is not a trained model, so treat the verdict as a lead. Nothing is stored.
About the PlayRight Failure Analyzer
The PlayRight Failure Analyzer takes the error message and call log of one failed Playwright test and tells you whether it looks like a locator, timing, data, app-bug or environment problem. You see the rules that fired, a confidence value, close alternatives, sturdier locators and fixes as JavaScript and Python code. The checks are regular-expression rules, not a trained model.
How to use the PlayRight Failure Analyzer
- Paste the failure output, including the Call log lines, and optionally the failing source line and whether the test failed on all retries or passed on a retry.
- Press Analyze failure to get the category, confidence, evidence and the suggested fixes, and switch between the JavaScript and Python code tabs.
- Download the verdict as Markdown or JSON to attach it to a ticket, then check the suggested change against your page before applying it.
Frequently asked questions
What should I paste?
The error text exactly as Playwright prints it, including the Call log section with lines such as waiting for locator and locator resolved to 0 elements. The source line, stack and captured output are optional but improve the result.
Why does it sometimes say unknown?
When no category reaches a score of 4 the analyzer does not guess. Unusual errors, or messages cut off before the call log, usually end up there; paste more of the output.
What do the retry checkboxes change?
They set the failed-on-all-attempts, passed-on-a-retry and same-message flags. A test that passed on a retry points to timing or shared data, one that fails every time points to a locator, data or app problem.
Can I call it from a script?
Yes. POST the same fields as JSON to /api/playright-analyze or use the command tf2cdk playright-analyze <file>; both return the same result as this page.
Is the pasted output stored when I use the Failure Analyzer?
The text you submit is processed in memory to produce the result and is not saved. Like any web server, Code Converter logs basic visit data (page, IP address and browser) but never the content you paste.