E2E Test Coverage Mapping

Analyze automated e2e tests and the project source code. Produce coverage.e2e.yml — a map from source files (or globs) to test identifiers (suite IDs, test IDs, tags) embedded in the test code. @testomatio/reporter run "<runner>" --filter "coverage:file=coverage.e2e.yml,diff=<branch>" consumes it to run only the e2e tests affected by the diff.

Critical Constraints

• Only automated e2e tests. No unit tests. No manual markdown cases (that is qa-manual-tests-to-code-coverage, if available).
• Do not suggest creating new tests.
• Only touch two files in this repo: the coverage file (default coverage.e2e.yml, or the path the user gave) and one .testeiya/ line in .gitignore if missing. Never a source or test file.
• Never clone tests into a tracked folder. External test repos go into the gitignored .testeiya/e2e-tests/ (Step 1).
• Don't write scripts. Never use Python. Read test files with your file tool; pull out IDs and tags with grep (Step 3). The only script is the bundled checker: npx js-yaml coverage.e2e.yml | node scripts/check-coverage.mjs (Step 6). If you ever need more than a grep, a one-line node -e '…' is the limit — never a parser of your own.

Workflow

Step 1: Discover the project

Run the scan-automation-project skill to inventory the project. Use its output as the source of truth — do not duplicate its scans here. Capture: