Skip to content
v0.3.0MIT

QA separated from dev: acceptance criteria with a usage oracle, scenario design with ISTQB techniques, automation with existing tools (Gherkin, Hurl, Testcontainers, Toxiproxy, Pact, Schemathesis, Playwright), verification by rungs with traceability and an integrity seal, failure classification and bug injection to test the tests. The implementing agent never writes the oracle and QA never certifies.

qa-test-the-tests

Tests the acceptance suite by injecting plausible bugs (mutants) into the diff's code, in temporary worktrees that never touch the repo, and reports which bugs survive; each survivor is a concrete gap in the scenarios. Use it when the user asks "are the tests any good?", "does the suite have teeth?", asks for "mutation testing", "bug injection" or "testing the tests", and as a gate of the full cadence (mandatory in solo mode).

License
MIT
Read SKILL.md at the source

Pinned to revision a2c346f89684, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.