writing-tests-against-stubs

To write TDD tests against frozen stubs, you must ensure the tests fail with the expected unimplemented marker and cover all acceptance criteria. This enforces proper test-driven development practices before implementation begins.

Verifying acceptance criteria coverage requires mapping every criterion from your design doc to a corresponding test. This ensures your test suite comprehensively validates all specified requirements against the frozen stubs.

Property-based testing for pure functions should be used to ensure robustness across a wide range of inputs. It complements standard stub testing by validating mathematical invariants and edge cases automatically.

Yes, this stub testing approach is specifically designed for the rpie three-phase flow. It requires strict adherence to TDD principles to effectively verify unimplemented markers and acceptance criteria.

Stub tests need to fail with an unimplemented marker to strictly verify that the test is checking the correct behavior before any logic is written. This prevents false positives and ensures proper TDD progression.

Testing against frozen stubs is limited to verifying acceptance criteria and unimplemented markers. It does not validate actual implementation logic, integration points, or runtime side effects outside the defined pure function boundaries.