Unit tests
Fast feedback on pure logic with mocks/fakes for IO; table-driven and boundary-focused—avoid testing implementation detail for coverage alone.
Category · Testing
Testing
5 skills Category 5 of 20
This category gives actionable strategies across the pyramid: unit tests and doubles, integration tests with containerized deps, E2E on critical paths, coverage gates with exceptions, and mutation testing to see if tests really exercise logic. It complements agent engineering evals—product regression vs. model/tool-call quality.
In the hub it is the dedicated “testing” band. The five entries match the main hub.
Quick links
In depth
Integration tests
Testcontainers, compose, etc., to run a slice of real deps and validate SQL, messaging, and external contracts—mind parallel isolation and data lifecycle.
E2E tests
Cover login, checkout, and other critical paths; control flakiness (waits, network, data) and tie to smoke envs and seed data.
Coverage strategy
Line/branch thresholds with waiver processes; tie “uncovered” to risk registers—coverage is a signal, not the goal.
Mutation testing
Mutate code to see if tests catch it—measures killing power; good periodic health checks on core modules, often wired into CI/CD gates.