e2e-test-writer

To generate an E2E test plan, the skill reads your repository to detect the test framework, maps the specified end-to-end flow, and proposes test cases covering happy paths, edge cases, and failure modes for your approval.

Automatic test framework detection works by using Read, Grep, and Glob to scan repository files like package.json, pyproject.toml, Gemfile, or go.mod, identifying the correct test entry points and data requirements for your E2E tests.

An E2E test plan should include test cases for happy paths, auth/permission checks, invalid inputs, dependency failures, and idempotency, ensuring tests are deterministic and independently runnable.

Yes, you can review and approve the E2E test cases. The skill generates a ready-to-implement test file outline and prompts for your explicit approval before writing the final test file.

You ensure E2E tests are deterministic by mapping data prerequisites, entry points, and teardown steps. The generated test plan outlines these independently runnable steps to prevent test interference.

Yes, the E2E test generation tool works with different programming languages by detecting framework signals across multiple dependency files, allowing you to apply it to any flow in a codebase requiring an E2E test.