Automate browser-level E2E test generation, review, and verification with Playwright.
npx skills add https://github.com/ValueMedia/10xcards-td --skill 10x-e2e-valuemedia
Please help me install this Agent Skill. Skill: 10x-e2e Source: https://github.com/ValueMedia/10xcards-td/tree/main/.opencode/skills/10x-e2e Command: npx skills add https://github.com/ValueMedia/10xcards-td --skill 10x-e2e-valuemedia
This Skill automates the execution of browser-level (E2E) test phases against a running app, driving test generation, review, and verification for risks that genuinely require a browser and whose feature is already built.
/10x-implement and /10x-tdd, allowing for interleaving of different testing types.Use the 10x-e2e skill to drive the E2E test phase for the 'change-id' and optional 'phase N'.
High-intent search queries and answers about installing and using this skill.
You automate E2E testing for cross-boundary risks by driving a plan, generate, review, and verify cycle using Playwright. This approach targets complex user flows that genuinely require browser-level coverage to validate functionality.
Risk-driven browser testing is an approach that generates and verifies tests specifically for cross-boundary risks. You need it when an app's complex user flows involve multiple system boundaries and require end-to-end testing to verify functionality.
Yes, you need Playwright configured as a dependency, along with a single spec run configuration and a way to start the app. The feature to be tested must also already be implemented before driving eligible E2E tests.
Yes, you can interleave E2E testing with other testing types because the skill shares progress tracking with implementation and TDD workflows. This shared tracking allows you to manage different testing phases concurrently.
The best way to ensure high-quality E2E test generation is to utilize a seed test and specific E2E rules during the generation phase. These quality levers guide the creation of reliable tests for cross-boundary risks.
You should not use browser-level E2E testing for unimplemented features because the process requires the feature to already be built. It drives only eligible E2E tests against a running app to verify existing functionality.
olehsvyrydovAutomate end-to-end tests for web and mobile apps with Playwright and Detox.
eventua11yAutomate E2E and unit test setup and execution with Playwright and Vitest.
lgwanaiGenerate unit and E2E tests from SUMMARY, CONTEXT, and VERIFICATION specs.
nguyenpv1980-wqWrite Vitest unit and component tests with environment selection and deterministic mocks.