Debug E2E Test
bitovi/ai-enablement-prompts
Debug and fix failing Playwright E2E tests. An agent skill from bitovi/ai-enablement-prompts.
Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.
Install Fix Failing Playwright Spec
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install appsmithorg/appsmith fix-pw-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .claude/skills/fix-pw-spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .claude/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install appsmithorg/appsmith fix-pw-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .agents/skills/fix-pw-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .agents/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install appsmithorg/appsmith fix-pw-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .cursor/skills/fix-pw-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .cursor/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/appsmithorg/appsmith.git --path .cursor/skills/fix-pw-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install appsmithorg/appsmith fix-pw-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .gemini/skills/fix-pw-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .gemini/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install appsmithorg/appsmith fix-pw-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .github/skills/fix-pw-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .github/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appsmithorg/appsmith --skill fix-pw-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install appsmithorg/appsmith fix-pw-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appsmithorg/appsmith.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/fix-pw-spec .opencode/skills/fix-pw-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fix-pw-spec" agent skill from https://github.com/appsmithorg/appsmith/tree/release/.cursor/skills/fix-pw-spec into .opencode/skills/fix-pw-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-pw-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fix-pw-spec- GitHub stars
- 41k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 449 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.
- Works in 5 steps: Gather Failure Context → Classify the Error → Fix Using Conventions → …
- A Playwright test fails because of selectors, waits or assertions
- SKILL.md covers When to Use, Step 1 — Gather Failure Context, Step 2 — Classify the Error and Step 3 — Fix Using Conventions, plus 3 more sections
- Calls npx
What it does
The skill is for bugs in test code, not in the product: wrong selectors, bad waits, incorrect assertions and code errors. It gathers the Playwright error output, the failing spec and the trace or screenshots from the results folder. If the product itself is broken, it hands off to the separate diagnose-pw-failure skill.
A table classifies error patterns and pairs each with a fix. Timeouts waiting for a locator mean updating the selector, strict mode violations call for .first(), .nth() or a tighter locator, wrong expected text means checking the target element and test data, closed targets or failed navigation need waitForResponse or waitForURL, hidden elements need the right state or scrolling, and import errors need path fixes. ECONNREFUSED and net errors are deployment issues the spec cannot fix. Selector replacements follow a priority from getByRole, getByPlaceholder and getByTestId to the project's widget selector constants, with CSS selectors last.
When your agent uses it
- A Playwright test fails because of selectors, waits or assertions
- Fixing a flaky Playwright spec
- Interpreting a strict mode violation or a locator timeout
Example prompts
- “This Playwright spec is failing with a locator timeout. Find out why and fix it.”
- “Fix the flaky test in the datasources spec.”
- “Here is the trace folder from the failed run. Work out whether the spec or the product is wrong.”
Requirements
- A Playwright test setup with the failing spec and its error output
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 552488b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fix Failing Playwright Spec loads about 1.3k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 449 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from appsmithorg/appsmith at commit 552488b, republished under its Apache-2.0 licence (© appsmithorg). 449 words, ~1,256 tokens.
Download SKILL.mdSave it as
.claude/skills/fix-pw-spec/SKILL.md (or your agent's skills folder).- name
- fix-pw-spec
- description
- Fix a failing Playwright spec by analyzing error output, identifying the root cause in the test code, and applying corrections. Use when a Playwright test fails due to wrong selectors, bad waits, incorrect assertions, or code errors. Trigger phrases: "fix this playwright test", "this spec is failing", "playwright test broken", "fix the flaky test".
Fix Failing Playwright Spec
When to Use
This skill fixes test code bugs — not product bugs. Use it when:
- A spec you wrote (or someone else wrote) fails due to selectors, waits, or assertion logic
- The product behavior is correct but the test doesn't match it
- Playwright reports timeouts, strict mode violations, or wrong expected values
If the product itself is broken, use diagnose-pw-failure instead.
Step 1 — Gather Failure Context
Read these three things:
- The Playwright error output from the terminal (the test run output)
- The spec file that failed
- The trace or screenshot if available:
- Traces:
app/client/playwright/results/<test-path>/trace.zip - Screenshots:
app/client/playwright/results/<test-path>/*.png
- Traces:
Step 2 — Classify the Error
| Error pattern | Root cause | Fix |
|---|---|---|
Timeout waiting for locator("...") | Selector doesn't match any element | Inspect the actual page; update selector |
strict mode violation: locator resolved to N elements | Locator too broad | Add .first(), .nth(), or refine with chained locators |
expect(received).toHaveText("X") received "Y" | Wrong expected value OR wrong element | Verify which element you're targeting; update expected value if test data changed |
Target closed / page.goto: Navigation failed | Page navigated away before action completed | Add waitForResponse or waitForURL before the action |
locator.click: Element is not visible | Element exists but hidden (behind modal, off-screen) | Wait for the right state, scroll into view, or close blocking elements |
Cannot find module / TypeScript error | Import path wrong or missing export | Fix the import path; check that POM/helper exports the symbol |
ECONNREFUSED / net::ERR_* | Not a spec bug — deployment issue | Stop. This is not fixable in the spec. |
Step 3 — Fix Using Conventions
When fixing, follow the project conventions (from .cursor/rules/playwright.mdc):
Show full SKILL.md (189 more words)Show less
Selector fixes
Prefer this priority order when replacing a broken selector:
page.getByRole("button", { name: /submit/i })— bestpage.getByPlaceholder("Search...")— for inputs without proper label associationpage.getByTestId("my-element")— explicit contractpage.locator(SELECTORS.widgetInDeployed("text"))— Appsmith widget selectors from constants- CSS selector with comment — last resort only
Do not: Guess selectors. If unsure what's on the page, add a temporary await page.pause() or read the component source to find the actual DOM structure.
Wait fixes
Replace any hard waits or networkidle with specific conditions:
// Instead of waitForTimeout or networkidle, wait for the element:
await expect(page.getByRole("heading", { name: "Dashboard" })).toBeVisible();
// For mutations, wait for the API response:
const response = page.waitForResponse(r => r.url().includes(API.actionsExecute));
await page.getByRole("button", { name: "Save" }).click();
await response;Assertion fixes
Ensure all assertions use the auto-retrying form:
// WRONG — non-retrying
expect(await locator.textContent()).toBe("value");
// RIGHT — auto-retrying
await expect(locator).toHaveText("value");Step 4 — Re-run and Verify
After fixing, re-run the specific test:
cd app/client && npx playwright test <spec-file> --project=<project>If it still fails, go back to Step 2 with the new error output.
Budget: Max 3 fix attempts per failure. After 3, either:
- The spec is fundamentally wrong (rewrite from scratch)
- The product has a bug (switch to
diagnose-pw-failure)
Step 5 — Validate Fix Quality
Before declaring the fix done, check:
- No
networkidleintroduced - No
waitForTimeoutintroduced - No hardcoded API URLs or CSS selectors
- Assertions use auto-retrying
expect - No unused imports left behind
- Run
npx eslint <file> --ext .tsclean
Output
Summarize what was wrong and what was fixed:
## Spec Fix Summary
**File**: playwright/tests/sanity/widgets/table-filter.spec.ts
**Attempts**: 2
### Fix 1
- **Error**: Timeout waiting for locator `getByRole("button", { name: "Filter" })`
- **Cause**: Button text is "Add Filter", not "Filter"
- **Fix**: Updated to `getByRole("button", { name: /add filter/i })`
### Fix 2
- **Error**: strict mode violation on `.first()` table row
- **Cause**: Filter hadn't applied yet when assertion ran
- **Fix**: Added `waitForResponse` on the execute API before asserting row content
**Result**: PASS© appsmithorg, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/fix-pw-spec of appsmithorg/appsmith.
Open the folder on GitHubat commit 552488b
Compare with similar skills
Fix Failing Playwright Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fix Failing Playwright Spec this skillappsmithorg/appsmith | 41k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Debug E2E Testbitovi/ai-enablement-prompts | 121 | — | ~677 | Automated safety check: Pass | MIT | |
| Cucumber and Playwright E2E Testslanggenius/dify | 158k | — | ~682 | Automated safety check: Pass | Custom licence | |
| Debug Playwright Prowquay/quay | 2.8k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Testingkortix-ai/suna | 20k | — | ~3.6k | Automated safety check: Notes | Custom licence | |
| Debugging Opik E2E Testscomet-ml/opik | 22k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Debug Playwright Prow
quay/quay
Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…
Testing
kortix-ai/suna
A skill your agent uses for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark…
Debugging Opik E2E Tests
comet-ml/opik
Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.
Quay Prow Triage
quay/quay
Diagnose any Quay Prow job failure end to end: prowjob.json - top-level build log - JUnit - resolved failing step - Playwright results.json when the failing step is Playwright, continuing through…
More from appsmithorg/appsmith
Write and Verify Playwright Tests
appsmithorg/appsmith
Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Related
Works with
Categories
Questions about Fix Failing Playwright Spec
What does Fix Failing Playwright Spec do?
Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions. The skill is for bugs in test code, not in the product: wrong selectors, bad waits, incorrect assertions and code errors. It gathers the Playwright error output, the failing spec and the trace or screenshots from the results folder.
When should I use Fix Failing Playwright Spec?
Fix Failing Playwright Spec fits situations like: A Playwright test fails because of selectors, waits or assertions; fixing a flaky Playwright spec; interpreting a strict mode violation or a locator timeout.
How do I install Fix Failing Playwright Spec in Claude Code?
Run `npx skills add appsmithorg/appsmith --skill fix-pw-spec -a claude-code`. Or copy the skill folder (.cursor/skills/fix-pw-spec in appsmithorg/appsmith) into .claude/skills/fix-pw-spec in your project. Claude Code loads it when a task matches its description.
How do I install Fix Failing Playwright Spec in Codex?
Run `npx skills add appsmithorg/appsmith --skill fix-pw-spec -a codex`. Or copy the skill folder (.cursor/skills/fix-pw-spec in appsmithorg/appsmith) into .agents/skills/fix-pw-spec in your project. Codex loads it when a task matches its description.
Can I use Fix Failing Playwright Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appsmithorg/appsmith --skill fix-pw-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-pw-spec, .gemini/skills/fix-pw-spec, .github/skills/fix-pw-spec and .opencode/skills/fix-pw-spec in your project.
What does Fix Failing Playwright Spec need to run?
Going by SKILL.md and its folder, Fix Failing Playwright Spec needs the command-line tools its instructions call (npx). Our summary lists: A Playwright test setup with the failing spec and its error output.
Does Fix Failing Playwright Spec access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Fix Failing Playwright Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fix Failing Playwright Spec use?
Fix Failing Playwright Spec is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fix Failing Playwright Spec use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fix Failing Playwright Spec?
Skills that share tags, products or a category with Fix Failing Playwright Spec: Debug E2E Test (bitovi/ai-enablement-prompts, 121 stars), Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars), Debug Playwright Prow (quay/quay, 2.8k stars) and Testing (kortix-ai/suna, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fix Failing Playwright Spec?
appsmithorg (a GitHub organization) maintains it in appsmithorg/appsmith, which has 41,030 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.
Source: appsmithorg/appsmith on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.