What problem does it solve?
Adding or changing API endpoints without end-to-end coverage leaves critical API behaviour untested, and writing tests without following the project's established architecture creates inconsistent, unmaintainable suites.
Core Features & Use Cases
- Guided e2e test authoring: Writes or extends API end-to-end tests aligned with ADR-0012 (runtime, isolation, scope) and ADR-0013 (suite organisation, helpers, conventions).
- Suite execution workflow: Runs the affected suite via the public-api-e2e-tests.sh entrypoint and iterates until tests pass.
- Scope guardrails: Distinguishes API e2e testing from unit tests and avoids seeding databases directly, preferring API-created fixtures.
- Use Case: After adding a new Public API endpoint, use this Skill to add a contract test to the existing suite, run it locally, and document any coverage gaps.
Quick Start
Write an end-to-end test for the new Public API endpoint I just added and run the e2e suite to verify it passes.