e2e-check

Automate end-to-end testing and interactive browser verification with Playwright.

64|19|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill e2e-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-check
Source: https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/e2e-check
Command: npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill e2e-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of end-to-end tests or allows for interactive browser-based verification, saving time and reducing manual effort in testing web applications.

Core Features & Use Cases

  • Automated E2E Testing: Execute test suites with Playwright, providing automated testing for web applications.
  • Interactive Browser Verification: Perform manual verification using Playwright's Manual Control Panel (MCP) tools.
  • Use Case: When you need to ensure that a new feature on your web application works as expected, you can use this Skill to run the automated tests or manually verify the functionality in the browser.

Quick Start

Run the end-to-end tests for your project by executing the command: /e2e-check [project] [test-filter] [--interactive].

Frequently Asked Questions about e2e-check

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

FAQPage Schema
How do I automate end-to-end testing for web applications using Playwright?

Automate end-to-end testing by executing test scripts with Playwright to verify web application functionality, saving time and reducing manual effort in continuous integration scenarios.

Can I perform interactive browser verification for manual testing scenarios?

Yes, interactive browser verification is supported using Playwright's Manual Control Panel tools, allowing you to manually verify new web application features directly in the browser.

What is the best way to run filtered end-to-end tests for a specific project?

Run filtered end-to-end tests by executing the command with your project name and a test filter, allowing you to target specific test suites for your web application verification.

Do I need Playwright installed to execute browser testing scripts?

Yes, Playwright and its associated testing frameworks are required dependencies for executing test scripts and running end-to-end browser verification for web applications.

Does this end-to-end testing approach work for continuous integration environments?

Yes, end-to-end testing with Playwright is suitable for continuous integration environments, automating test suite execution to ensure web application features work as expected.

When should I use interactive browser verification instead of automated end-to-end tests?

Use interactive browser verification when manually checking new web application features, and use automated end-to-end tests when running comprehensive test suites in continuous integration pipelines.