← ClaudeAtlas

cucumber-testslisted

Use when writing, changing or debugging an acceptance test in this repo — Cucumber scenarios, Gherkin, .feature files, step definitions, @AC- tags, acceptance criteria, or a failing npm run test:e2e. Also use before adding new user-visible behaviour, which needs a criterion and a scenario before it is done.
ydbondt/shkills · ★ 0 · Testing & QA · score 62
Install: claude install-skill ydbondt/shkills
# The Cucumber suite Unit tests say the parts work. This suite says the product works: real server, real browser, real CLI. Scenarios are written to read as the promise being made, not as the code being called. [`docs/e2e-testing.md`](../../../docs/e2e-testing.md) is the reference — the full step vocabulary, the wiring, the debugging recipes. Read it when you need a step. What follows is only the part that is easy to get wrong. ## The criterion comes first `docs/acceptance-criteria.md` is the specification; the features are the proof. New user-visible behaviour is not done until both exist. 1. Add the criterion to `docs/acceptance-criteria.md`, in the right section's table, as **`| **AC-n** | … | P |`**. The id must be **bold** — the coverage check greps for `\*\*(AC-\d+)\*\*` and will not see it otherwise. 2. Tag the scenario `@AC-n` in the feature file for its area. `npm run test:e2e -w @shkills/e2e` runs `check-coverage.mjs` *before* Cucumber, so an unclaimed criterion or a tag pointing at a criterion that does not exist fails the run without executing a single scenario. It checks both directions on purpose: a mapping that has rotted quietly is worse than no mapping. ## Writing the scenario **Set up through the API, assert through the interface a person uses.** `Given these people:`, `… has published the skill …`, `a collection … containing:` put the world in position. The portal and the terminal are for the thing the scenario is actually about. Clicking a fi