testing

To enforce deterministic testing, you must eliminate network calls in unit tests, ensure test isolation, and maintain reproducible environments. This approach guarantees repeatable results by aligning test planning and triage with documented testing policies.

A Testing State Capsule is a repository context artifact that tracks test planning, implementation, and triage progress. It guides testing workflows by maintaining state across unit and integration layers to ensure repeatable test coverage.

Writing unit and integration tests for multi-language repositories requires aligning with AGENTS.md and docs/testing-policy.md. You establish a baseline by running the smallest, fastest tests first, then expand coverage while updating the Testing State Capsule.

No, applying this testing guidance requires repository context including AGENTS.md and docs/testing-policy.md. These files provide the necessary deterministic testing principles and workflow rules to properly plan and triage tests.

Running the smallest, fastest tests first establishes a quick baseline to verify test isolation and reproducible environments. This strategy allows you to expand unit and integration coverage incrementally while avoiding flaky tests.