generate-test-cases

Convert exploration reports and coverage plans into structured test cases by processing shared evidence like e2e-plan artifacts. The skill generates per-feature TC-ID specifications under test-cases, preserving real URLs, selectors, and artifact references for QA teams.

Yes, you can generate non-happy-path test case specifications from markdown evidence. The skill enforces structured output that groups cases by feature and includes both happy-path and non-happy-path scenarios for comprehensive web app coverage.

Create TC-ID test cases without writing executable tests by providing a feature URL and journey description. The skill transforms existing coverage artifacts into detailed markdown specifications suitable for automation pipelines.

Existing coverage artifacts are helpful but not strictly required. The skill primarily processes e2e-plan evidence like exploration-report.md and coverage-plan.md, using available artifact references to enrich the generated test case files.

Grouping test cases by feature works by parsing coverage plans and exploration reports to identify distinct web app features. The skill then generates individual markdown files under test-cases for each feature, maintaining structured TC-ID formatting throughout.

A key limitation is that the skill generates markdown specifications, not executable automation code. It focuses on structuring evidence into TC-ID specs for QA teams, meaning downstream automation pipelines require separate implementation steps.