skills.rest
StudyDrift
StudyDriftOFFICIAL
Explore all skills by this author →
𝕏@studydriftGitHub

run-smoke-tests

Run Playwright smoke tests to verify frontend application health.

58|5|Updated Aug 30, 2024
Search Tags:#debugging#logs#playwright#e2e-testing#root-cause-analysis#smoke-testing
One-click install
npx skills add https://github.com/StudyDrift/lextures --skill run-smoke-tests-studydrift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-smoke-tests
Source: https://github.com/StudyDrift/lextures/tree/main/.cursor/skills/run-smoke-tests
Command: npx skills add https://github.com/StudyDrift/lextures --skill run-smoke-tests-studydrift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end smoke verification helps teams catch critical regressions early by validating core user flows after changes.

Core Features & Use Cases

  • Execute smoke suites: Run end-to-end checks to validate critical user paths.
  • Targeted testing & debugging: Focus on specific test files or scenarios and inspect traces to identify root causes.
  • Quicker iteration: Re-run after fixes to ensure stability and prevent flaky releases.

Quick Start

Run the full smoke suite with npm run smoketest to verify end-to-end stability.

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 frontend app health?▼

Playwright smoke tests isolate test failures by capturing detailed execution logs and inspecting traces to identify root causes. This enables targeted debugging of specific scenarios and quick iterative re-runs to ensure application stability.

Can I target specific test files for debugging instead of running the full smoke suite?▼

Yes, you can target specific test files or scenarios for debugging to focus your verification efforts. This allows you to inspect traces and isolate the root cause of failures without waiting for the entire end-to-end smoke suite to complete.

What is the best way to stabilize flaky end-to-end releases?▼

The best way to stabilize flaky end-to-end releases is to run iterative smoke tests after applying fixes. Re-running targeted checks ensures deterministic test execution and confirms that critical user paths remain stable before deployment.

Do I need a frontend web app to use end-to-end smoke verification?▼

Yes, end-to-end smoke verification applies specifically to frontend web apps that require quick health checks. It is designed to validate critical user paths within web interfaces rather than backend services or APIs.

Related Skills

Explore More Software Engineering Skills→
cursorcursor
2.6k

run-smoke-tests

Run Playwright smoke tests and produce logs with failure traces.

Official
Intermediate
Marwan78888Marwan78888
16

debugging-wizard

Analyze error messages, stack traces, and logs to identify and resolve software issues.

Community
Advanced
allanninalallanninal
1

root-cause-tracing

Trace stack traces and logs to identify root causes of software failures.

Community
Intermediate
cenjiecenjie

frontend-testing

Implement frontend tests for React and Vue with Jest, Vitest, React Testing Library, and Cypress.

Community
Intermediate