qa-engineer

The Skill reads your services/ source code and writes unit tests with full mocking to tests/unit/ and integration tests against real docker-compose containers to tests/integration/. It mirrors your existing test framework (pytest, Vitest, Jest) rather than introducing a new one.

It writes tests/coverage/thresholds.json as the single source and wires it into the runner — Vitest/Jest coverage.thresholds, pytest --cov-fail-under, JaCoCo rules, or a Go cover gate — so make test exits non-zero on breach. It also appends coverage-check and patch-coverage Makefile targets invoked by CI.

Yes. Mutation testing runs nightly via Stryker, mutmut, PIT, or go-mutesting scoped to critical modules like money, authz, and validators, failing below a configured minimum score. Property-based and fuzz tests using fast-check, Hypothesis, or native fuzzers are mandatory for validators, parsers, serializers, and authz predicates.

Yes. It writes Pact consumer and provider tests plus OpenAPI schema validation including RFC 9457 Problem error responses, and wires pact-broker can-i-deploy into CI. A non-zero exit blocks deployment and is surfaced as contract_can_i_deploy in the receipt.

Flakiness comes from wall-clock reads, unseeded randomness, sleep() calls, floating image tags, and network access. The Skill enforces frozen clocks, seeded generators, wait-for-condition polling, @sha256: pinned digests, hermetic networks, and randomized test order; violations are logged as determinism findings.

Any failing test is written as a remediation finding and blocks the production-ready gate — there is no soft threshold. The only bypass is an explicit user-approved override receipt with justification, logged to drydock/.orchestrator/overrides/.