run-tests

Execute Playwright test suites in local, CI, and interactive modes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cottage-Energy/cottage-tests --skill run-tests-cottage-energy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/run-tests
Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill run-tests-cottage-energy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through executing Playwright tests across local, CI, and interactive modes, simplifying validation and debugging.

Core Features & Use Cases

  • Local execution: run specific tests or suites on your machine for quick validation.
  • CI execution: trigger remote workflows for full regression and cross-browser coverage.
  • Interactive walkthrough: step through flows using Playwright MCP to debug UI behavior and verify state.

Quick Start

Choose a mode (Local, CI, or Interactive) and specify the test scope to begin execution.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I run Playwright e2e tests locally for quick validation?

To run Playwright e2e tests locally, execute specific tests or suites on your machine to accelerate validation. You can target end-to-end tests organized under tests/e2e_tests using optional tags and scope controls for precise selection.

Can I trigger Playwright tests in CI for full regression and cross-browser coverage?

Yes, you can trigger remote CI workflows to execute Playwright test suites for full regression and cross-browser coverage. This CI execution mode simplifies validation by running comprehensive tests automatically across different environments.

What is interactive mode for Playwright tests and how does it help debugging?

Interactive mode is an execution approach that steps through Playwright test flows to debug UI behavior and verify state. It uses Playwright MCP to provide an interactive walkthrough, helping you identify issues during end-to-end test validation.

How do I handle timeouts and generate reports when running e2e tests?

You handle timeouts and generate reports by following robust guidance for execution modes during e2e tests. This process produces visual outputs including screenshots and HTML reports to help debug and verify test results.

Does this test execution approach support selecting specific test scopes with tags?

Yes, test execution supports selecting specific test scopes using optional tags. You can target end-to-end tests organized under tests/e2e_tests with precise scope controls to run only the validation suites you need.

What is the best way to debug Playwright UI behavior during end-to-end tests?

The best way to debug Playwright UI behavior is using interactive mode to step through test flows. This interactive walkthrough leverages Playwright MCP to verify state and pinpoint UI issues during end-to-end test execution.