test-designer

To write failing tests without bias, use independent evaluation where tests are designed without seeing the implementation. This prevents biased implementations and ensures correct behavior is established before coding begins.

Independent evaluation in TDD is designing tests without visibility into the feature implementation. It is needed during the red phase for non-trivial features with ambiguous requirements or risk of biased tests.

To ensure edge-case coverage, enumerate boundary, concurrency, lifecycle, invariant, and adversarial inputs during test design. This approach validates complex feature behavior against diverse and unexpected conditions.

Yes, this test design workflow is specifically applied during the red phase of TDD for non-trivial features with ambiguous requirements. It produces executable test artifacts that fail against incomplete implementations.

Failing tests guide subsequent coding by providing incremental guidance through an explicit test design workflow. They indicate exactly what to implement and validate during the red-green-refactor loop.

Independent failing tests are designed for non-trivial features with ambiguous requirements or bias risk. For simple features, this explicit test design workflow may introduce unnecessary overhead without proportional benefits.