Run Smoke Tests
- 1.3k installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
Run Smoke Tests is a Cursor plugin skill that executes Playwright smoke suites, debugs failures from traces and logs, and reruns until core plugin commands and integrations stay stable.
About
Run Smoke Tests is a skill from cursor/plugins for end-to-end smoke verification of Cursor plugins using Playwright. The workflow builds prerequisites, runs npm run smoketest or a focused spec such as path/to/test.spec.ts, inspects traces and logs on failure, applies minimal fixes, and reruns until stable. It documents npm run smoketest-no-compile for faster iteration when build artifacts already exist. Developers reach for it after plugin changes to confirm activation, commands, and integrations still work before merge or release.
- Fast post-change verification
- Cover core activation paths
- Catch breaking regressions early
- Minimal CI-friendly suite
- Gate merges on green smoke
Run Smoke Tests by the numbers
- 1,280 all-time installs (skills.sh)
- +201 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #507 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill run-smoke-testsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.3k |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
How do you smoke test a Cursor plugin?
Execute fast end-to-end smoke tests on a Cursor plugin after changes to confirm core commands, activation, and integrations still work.
Who is it for?
Cursor plugin maintainers who need fast Playwright smoke verification before or after modifying commands and integrations.
Skip if: Full performance benchmarking or unrelated application E2E suites outside the Cursor plugin smoke harness.
When should I use this skill?
Cursor plugin changed and end-to-end smoke verification is needed before merge, release, or after a failing smoketest run.
What you get
Passing Playwright smoke suite results, failure traces, root-cause notes, and verified plugin activation after fixes.
- smoke test pass results
- failure trace analysis
- minimal fix patches
Files
Run smoke tests
Trigger
Need end-to-end smoke verification before or after changes.
Workflow
1. Build prerequisites for the target app. 2. Run the relevant smoke suite or a focused test file. 3. If failing, inspect traces/logs and isolate the root cause. 4. 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.tsGuardrails
- 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
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kHow it compares
Use for quick plugin smoke gates; expand to full regression suites when broad coverage is required beyond core commands.
FAQ
Which commands does Run Smoke Tests use?
Run Smoke Tests runs npm run smoketest for the full suite, npm run smoketest -- path/to/test.spec.ts for a focused file, and npm run smoketest-no-compile when build artifacts are already ready for faster iteration.
What is the Run Smoke Tests failure workflow?
Run Smoke Tests builds prerequisites, executes the smoke suite, inspects Playwright traces and logs to isolate root cause, applies a minimal fix, and reruns until the Cursor plugin smoke tests pass.