run-smoke-tests
cursor/plugins
Run Playwright smoke tests, debug failures, and verify fixes
What is run-smoke-tests?
Automates end-to-end smoke testing using Playwright, helping you verify application functionality before or after changes. Includes debugging capabilities to isolate failures and validate fixes.
- Run full smoke test suites or focused test files
- Debug test failures by inspecting traces and logs
- Isolate root causes of test failures
- Apply and verify minimal fixes with re-runs
- Support faster iteration with pre-compiled build artifacts
- Identify and report flaky test risks
How to install run-smoke-tests
npx skills add https://github.com/cursor/plugins --skill run-smoke-tests- Node.js and npm installed
- Playwright configured in the project
- npm scripts for smoketest and smoketest-no-compile available
How to use run-smoke-tests
- 1.Build prerequisites for your target application
- 2.Run the full smoke suite with npm run smoketest or a specific file with npm run smoketest -- path/to/test.spec.ts
- 3.If tests fail, inspect traces and logs to identify the root cause
- 4.Apply a minimal fix to the code
- 5.Re-run the tests with npm run smoketest-no-compile for faster iteration until stable
Use cases
- Verify application stability before deploying changes
- Debug failing end-to-end tests in CI/CD pipelines
- Validate bug fixes with smoke test re-runs
- Perform quick smoke verification on specific test files
- Reduce flaky test false positives through deterministic assertions
- QA engineers
- Frontend developers
- CI/CD pipeline maintainers
- Test automation specialists
run-smoke-tests FAQ
Use the full suite for comprehensive pre-deployment verification. Use a specific test file when debugging a particular feature or iterating on a fix.
It skips the build step and runs tests directly against pre-compiled artifacts, enabling faster iteration when you're only changing test logic or application code without rebuilding.
Use deterministic waits and assertions instead of brittle timeouts, and re-run passing fixes to confirm stability before considering them resolved.
Test results summary, root cause analysis of failures, and any remaining flake risk assessment.
Full instructions (SKILL.md)
Source of truth, from cursor/plugins.
name: run-smoke-tests description: Run Playwright smoke tests, debug failures, and verify fixes
Run smoke tests
Trigger
Need end-to-end smoke verification before or after changes.
Workflow
- Build prerequisites for the target app.
- Run the relevant smoke suite or a focused test file.
- If failing, inspect traces/logs and isolate the root cause.
- Apply a minimal fix and rerun until stable.
Example Commands
# Run full smoke suite
npm run smoketest
# Run a specific smoke test file
npm run smoketest -- path/to/test.spec.ts
# Faster iteration when build artifacts are ready
npm run smoketest-no-compile -- path/to/test.spec.ts
Guardrails
- Prefer deterministic waits and assertions over brittle timeouts.
- Re-run passing fixes to reduce flaky false positives.
- Quarantine tests only when explicitly requested and documented.
Output
- Test results summary
- Root cause and fix
- Remaining flake risk (if any)
Related skills
More from cursor/plugins and the wider catalog.
setup-pstack
Agent skill from cursor/plugins.
show-me-your-work
Maintain a reviewable decision log (TSV) for long-running or autonomous work, with one row per decision.
swarm
Fan out N parallel workers, drain them, and return one consolidated report.
tdd
Write focused regression tests before fixing bugs with clear, cheap test paths.
teach
Explain code and systems plainly by combining how and why analysis into one clear account.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google style, STE rules, Global English syntax.