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-automation

Implements the approved scenarios as executable tests, with existing tools (Gherkin with godog, Hurl, Testcontainers, Toxiproxy, WireMock, Pact, Schemathesis, Playwright) and AI-generated plumbing; third-party learning tests first, then the scenarios, and it checks that each test fails for the right reason and is deterministic before sealing. Use it when the user asks to "automate the tests", "implement the scenarios", for "acceptance tests", "e2e tests", "learning tests" or after qa-test-design.

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.