openprd-test-strategy

A risk-based test strategy maps software requirements to specific test scopes based on complexity. It automatically routes verification to appropriate layers like unit, integration, or end-to-end environments to ensure comprehensive coverage.

Evidence-driven development enforces the creation of an evidence plan to prove software quality. It ensures testing claims are backed by verifiable runtime checks, logs, or visual comparisons rather than just stating tests were executed.

To document test execution evidence, you systematically log verification results across unit, integration, and end-to-end environments. This structured documentation ensures quality assurance through traceable proof of test outcomes.

Waiver justifications are needed in software testing when handling complex development workflows where standard verification is constrained. They provide structured reasoning for bypassing specific test layers while maintaining quality assurance.

Risk-based test routing works for UI components by evaluating the change to suggest appropriate testing layers. It determines whether you need visual regression tests, logic unit tests, or end-to-end flow tests for system integration.