playwright-cli-e2e

Execute a 12-group end-to-end regression suite for playwright-cli and diff results against a baseline.

28|14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ai-ecoverse/slicc --skill playwright-cli-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-cli-e2e
Source: https://github.com/ai-ecoverse/slicc/tree/main/packages/dev-tools/vfs-dev-skills/playwright-cli-e2e
Command: npx skills add https://github.com/ai-ecoverse/slicc --skill playwright-cli-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually testing the playwright-cli browser automation command for regressions after code changes is time-consuming, inconsistent, and easy to miss subtle broken functionality. This Skill eliminates that friction by providing a standardized, repeatable end-to-end test workflow.

Core Features & Use Cases

  • Standardized 12-group regression suite: Covers core browser interactions, network capture, console logging, route mocking, screenshots, HAR recording, and more, with both automated deterministic checks and manual visual/interactive test steps.
  • Baseline diffing: Automatically compares test results against a known PASS/FAIL baseline to flag regressions (previously passing tests that now fail) and improvements (previously broken tests that now pass).
  • Self-contained test fixture: Uses a built-in HTML test page that loads as a data URL with no external dependencies, ensuring consistent test conditions every run.
  • Use case: After modifying playwright-cli's click or screenshot functionality, use this Skill to quickly confirm no existing behavior was broken, without manually running dozens of individual test cases.

Quick Start

Run the playwright-cli-e2e skill to execute the full regression test suite for playwright-cli and review the PASS/FAIL diff against the known baseline.

Frequently Asked Questions about playwright-cli-e2e

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

FAQPage Schema
How do I automate e2e testing for playwright-cli regressions?▼

Automate playwright-cli regression testing by executing a standardized 12-group end-to-end test suite that diffs browser automation results against a known-good baseline to flag passing or failing tests.

What is baseline diffing in browser automation regression testing?▼

Baseline diffing in regression testing compares current e2e test results against a known PASS/FAIL baseline to automatically identify regressions in previously passing tests and improvements in previously broken ones.

How do I run a repeatable e2e test suite for browser interactions and network capture?▼

Run a repeatable e2e test suite by loading a self-contained HTML test fixture as a data URL with no external dependencies, executing core browser interactions, network capture, and route mocking checks.

Does the playwright-cli e2e test suite cover route mocking and HAR recording?▼

The playwright-cli e2e test suite covers route mocking and HAR recording alongside core browser interactions, console logging, and screenshots, utilizing both automated deterministic checks and manual visual test steps.

Can I integrate browser automation e2e test results into continuous testing pipelines?▼

You can integrate e2e test results into continuous testing pipelines by running the standardized test runner to produce machine-readable PASS/FAIL output for automated regression detection.

What are the limitations of manual visual test steps in e2e regression testing?▼

Manual visual test steps within e2e regression testing require human interaction for interactive validations, meaning full automation is limited to deterministic checks while visual confirmations remain manual.