FFT-Testing - TDD and Test Strategy
Overview
Section titled “Overview”FFT-Testing writes tests first. It enforces FlowForge Rule #3 — tests before code, 80% coverage minimum, and the correct test-location conventions for each language and framework. It designs test strategies that catch the regressions that matter without drowning the team in flaky specs.
Capabilities
Section titled “Capabilities”- TDD execution: red-green-refactor discipline, smallest-possible failing tests first.
- Unit testing: Jest, Vitest, pytest, Go test, JUnit 5 — idiomatic patterns for each.
- Integration testing: test containers, in-memory databases, contract tests between services.
- E2E testing: Playwright, Cypress, Detox; reliable selectors, trace-based debugging.
- Property-based testing: fast-check, Hypothesis, for invariants that example tests miss.
- Coverage analysis: branch coverage, mutation testing (Stryker, mutmut), dead-code detection.
- Test location enforcement: Rule #3 conventions — language-specific placement validated before merge.
- Flake remediation: root-cause analysis of intermittent failures, deterministic rewrites.
When to Use
Section titled “When to Use”- Starting any new feature — tests come first, always.
- Bringing an under-tested module up to the 80% coverage floor.
- Investigating and fixing flaky tests that are eroding CI trust.
- Designing a new layer’s test strategy before implementation begins.
Example Prompts
Section titled “Example Prompts”"Write failing tests for the pricing-snapshot feature before any implementation is started""Raise coverage of the src/billing module from 62% to 85% without adding trivial tests""Diagnose why the E2E checkout spec fails 1 in 20 runs and propose a deterministic rewrite"