10x-e2e

Automate Playwright end-to-end browser tests for critical application risks.

Updated May 25, 2026
One-click install
npx skills add https://github.com/bvshi/fodswap --skill 10x-e2e-bvshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-e2e
Source: https://github.com/bvshi/fodswap/tree/main/.agents/skills/10x-e2e
Command: npx skills add https://github.com/bvshi/fodswap --skill 10x-e2e-bvshi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the execution of end-to-end browser-level tests, significantly reducing the time and effort required for manual testing and ensuring comprehensive coverage of complex application features.

Core Features & Use Cases

  • End-to-End Test Execution: Drive browser-level (E2E) phases against the running app, one risk at a time.
  • Risk-Driven Approach: Focus on testing the most critical risks, ensuring that the most important aspects of the application are thoroughly tested.
  • Integration with Playwright: Leverages Playwright's capabilities for browser automation and testing.
  • Use Case: For a complex web application, use this Skill to automate the E2E testing process, ensuring that every critical feature is tested and any issues are identified early in the development cycle.

Quick Start

Run the 10x-e2e skill with the change ID and phase number, e.g., /10x-e2e <change-id> phase N.

Frequently Asked Questions about 10x-e2e

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

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

Automate end-to-end testing with Playwright by running the test skill against your running app, driving browser-level execution one risk at a time to ensure comprehensive coverage of complex features.

What is risk-driven testing and how does it apply to browser automation?

Risk-driven testing focuses browser automation on the most critical application risks first, ensuring the most important aspects of your web application are thoroughly tested by prioritizing complex feature validation over exhaustive coverage.

Do I need Playwright installed and configured before running automated E2E tests?

Yes, you need Playwright installed and configured in your environment, and the feature under test must already be implemented in your running application before executing automated E2E tests.

How do I execute a specific phase of end-to-end tests against a running application?

Execute a specific E2E test phase by running the skill command with your change ID and phase number, which drives browser-level test execution against the running app for that targeted risk phase.

Can I use this approach to test critical features early in the development cycle?

Yes, you can test critical features early in the development cycle by automating browser-level E2E test execution, which identifies issues in complex application features before they reach production.

What are the limitations of risk-driven end-to-end testing with Playwright?

Risk-driven E2E testing with Playwright requires the feature under test to be already implemented and the application running, focusing on critical risks rather than providing exhaustive test coverage of every possible scenario.