skills.rest
nthpaul
nthpaulCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

run-smoke-tests

Run Playwright smoke suites and focused spec files for pre- and post-change validation.

Updated May 18, 2025
Search Tags:#npm#smoke tests#playwright#e2e testing#CI verification#trace analysis#test debugging
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill run-smoke-tests-nthpaul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-smoke-tests
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/cache/cursor-public/cursor-team-kit/d1cdb88a9eb33cf392395c87e3fd76419fc1010e/skills/run-smoke-tests
Command: npx skills add https://github.com/nthpaul/dotfiles --skill run-smoke-tests-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent broken releases by running end-to-end smoke verification so failures are caught early and fixed with minimal regression risk.

Core Features & Use Cases

  • Run targeted Playwright smoke suites: Execute either the full smoke set or a focused spec to confirm fixes quickly.
  • Debug with actionable artifacts: Inspect traces/logs to isolate the root cause when failures occur.
  • Stabilize and reduce flakiness: Apply minimal fixes, rerun until stable, and avoid introducing brittle timing-based checks.

Quick Start

Run the full smoke suite for your application and use the reported failures to guide a minimal fix and rerun until it passes.

Frequently Asked Questions about run-smoke-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Playwright smoke tests to verify app health before a release?▼

Run Playwright smoke tests by executing the appropriate npm smoke command to verify application health and catch regressions early. This process builds prerequisites, runs the targeted smoke suite, and reports failures to guide minimal fixes before release.

What is the best way to debug failing e2e testing suites without introducing flakiness?▼

Debug failing e2e testing suites by inspecting Playwright traces and logs to isolate the root cause. Apply minimal fixes to stabilize the tests and rerun until they pass, avoiding brittle timing-based checks that introduce flakiness.

Can I run a focused Playwright spec file for post-change validation instead of the full smoke suite?▼

Yes, you can run a focused Playwright spec file for post-change validation to confirm fixes quickly. This targeted execution allows you to verify specific application changes without running the entire smoke suite, ensuring fast feedback.

Why does CI verification require running smoke suites before and after changes?▼

CI verification requires smoke suites before and after changes to prevent broken releases and minimize regression risk. Running end-to-end Playwright smoke validation catches failures early, ensuring fixes do not introduce new issues.

What should I do when trace analysis shows intermittent failures in my smoke tests?▼

When trace analysis shows intermittent failures in smoke tests, apply minimal fixes to stabilize the behavior and rerun until stable. Avoid introducing flaky timing practices, focusing instead on reliable end-to-end verification.

Related Skills

Explore More Software Engineering Skills→
sayalinvidiasayalinvidia

dynamo-router-starter

Configure and verify Dynamo frontend router modes across local and Kubernetes deployments.

Community
Advanced
paulbrittainpaulbrittain

run-smoke-tests

Run Playwright smoke tests and rerun until stable with traces and logs.

Community
Intermediate
OMIXECOMIXEC
1

e2e-testing-patterns

Automate Playwright and Cypress end-to-end test suites for web and mobile applications.

Community
Advanced
kanade0404kanade0404

tdd-workflow

Enforces test-first development for code across unit, integration and Playwright E2E workflows.

Community
Advanced