smoke-test

Automate local Playwright smoke tests with VRT and E2E checks.

1|Updated Sep 8, 2023
One-click install
npx skills add https://github.com/cmb-sy/dotfiles --skill smoke-test-cmb-sy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/cmb-sy/dotfiles/tree/main/claude/skills/smoke-test
Command: npx skills add https://github.com/cmb-sy/dotfiles --skill smoke-test-cmb-sy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables autonomous local smoke testing by orchestrating Playwright-based checks to validate feature behavior, visual regression baselines, and end-to-end flows after code changes.

Core Features & Use Cases

  • Environment setup + server bootstrapping: automatically starts and verifies a dev server on an available port.
  • Ad-hoc scenario generation: derives test scenarios from design diffs or code changes and executes them.
  • VRT & E2E validation with flaky detection: runs visual regression tests and end-to-end tests, identifying flaky tests and producing actionable reports.
  • Cancelable/step-wise execution: supports skipping steps and running in full or targeted modes.

Quick Start

Start the smoke-test and let it auto-run all steps from environment setup to E2E checks.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate local Playwright smoke tests after code changes?

Automate local Playwright smoke tests by orchestrating environment setup, server bootstrapping, and ad-hoc E2E scenario generation from design diffs. The smoke test validates feature stability, runs visual regression tests, and produces actionable reports with flaky detection.

What is visual regression testing with flaky detection and how does it work?

Visual regression testing compares UI snapshots to baselines to catch unintended visual changes. Flaky detection identifies inconsistent test results across runs, producing actionable reports that flag unreliable tests during your E2E and VRT validation checks.

Can I generate ad-hoc E2E test scenarios from design diffs automatically?

Yes, you can generate ad-hoc E2E test scenarios from design diffs or code changes. The smoke test derives targeted scenarios automatically and executes them against your local dev server to verify feature behavior after updates.

Do I need Playwright pre-installed to run local E2E smoke tests?

Yes, you need Playwright pre-installed along with a compatible Node.js or Python runtime. The smoke test also requires access to a configured repository to identify server commands, test suites, and optional inputs like diff-base or design paths.

What's the best way to run targeted smoke tests instead of a full suite?

Run targeted smoke tests using the step-wise execution mode, which supports skipping steps. This allows you to bypass full environment setup and run specific VRT or E2E checks independently based on your current testing needs.

Why does my local dev server need to be bootstrapped for E2E testing?

Bootstrapping the dev server ensures a stable, isolated environment for E2E testing. The smoke test automatically starts and verifies a dev server on an available port before executing scenarios, preventing port conflicts and ensuring consistent test execution.