Software Testing Strategy for Agentic Change
Define a complete testing system for changes produced or maintained by agents.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Design the test portfolio for a payment API schema change with a browser client, batch consumer, performance SLO, and accessibility requirement. Add one flaky test and one incomplete dependency map.
4. Tradeoffs and alternatives
Full suites maximize breadth and can make feedback unusably slow. Impact-based selection increases speed and depends on trustworthy mappings. Mutation and fuzz testing find important gaps but should be targeted by risk and budget. Browser and visual tests improve journey confidence while requiring stable data and rendering controls.
5. Current Mission Control Implementation
The current guide defines quality contracts, criterion-linked evidence, deterministic validation, independent verification, browser testing, security scanning, and replay. The golden-path lab requires unit, integration, and browser evidence.
It does not yet provide a complete test taxonomy, impact-analysis contract, flaky-test operating model, mutation or property-based strategy, performance and accessibility gates, or test-data lifecycle. This chapter establishes those missing responsibilities.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence