mcpField
E
e2e-test-generator

e2e-test-generator

github.com/nextstage-brasilTesting & quality041 installsUpdated 5d ago
Repository

About e2e-test-generator

A planning skill for generating Markdown E2E test tasks from a feature and frontend tasks. It is intended for teams using Cypress and requires an explicit data-testid contract rather than inventing selectors.

Key features

  1. 01Creates E2E task files with coverage strategy
  2. 02Requires frontend data-testid contract
  3. 03Plans desktop, tablet, and mobile coverage
  4. 04Includes success, error, and URL-based RBAC scenarios
  5. 05Defines Cypress paths and validation criteria

Use cases

  1. 01Planning E2E coverage after a frontend feature task
  2. 02Checking access-control behavior across URLs
  3. 03Organizing Cypress specs for different device sizes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill e2e-test-generator

After installing, type/e2e-test-generatorin Claude Code to confirm it loaded.

Bundled filesevals/evals.json

Details

From the project README

E2E Test Task Generator

Planning-phase skill: produce E2E task markdown. Execution-phase: create-e2e-tests.

Boundary

PhaseSkill
Planning (task file)e2e-test-generator
Implementation (Cypress code)create-e2e-tests

Harness discovery

Load {harness}/rules/e2e-tests-rules.mdc and frontend-rules.mdc when present.

Inputs

  • Feature to cover
  • Frontend implementation task(s) with data-testid contract
  • If contract missing → stop and request frontend task update

E2E project location

Default (greenfield): {product_root}/tests-e2e/ — independent Node package; paths below are relative to that root.

Brownfield: use detected Cypress root (tests-e2e/, legacy testes-cypress/, or frontend/). Do not plan new specs under frontend/cypress/ when no E2E exists yet.

Output highlights

Task file must include:

  • Summary and detailed coverage strategy
  • E2E root — tests-e2e/ (or detected brownfield path)
  • data-testid contract table (copied from frontend task — do not invent)
  • Spec paths under tests-e2e/cypress/e2e/device/{desktop|tablet|mobile}/[feature]/ (adjust prefix if brownfield)
  • Command files under tests-e2e/cypress/support/commands/ — shared/, pages/, device/
  • Bootstrap note when project has no E2E yet: executor must run create-e2e-tests Phase 0 before specs
  • Success, error, and RBAC by URL scenarios
  • Device coverage matrix
  • Validation criteria: no fixed cy.wait(N), commands not DOM in specs, @smoke/@regression tags

Dependencies

Depends on frontend implementation task for the same feature.

Docker note

When E2E runs in container: API URL via host gateway, not localhost inside container — per infra rules when present.

Related skills

  • create-e2e-tests — write/refactor Cypress code
  • task-generator — frontend tasks with testid contract

Comments

Markdown supported