← Graph

Test Driven Development

concept 8 connections

Ladd reframes TDD beyond the 'write a test, make it pass, refactor' mechanics: TDD's real object is improving the quality of designs and implementations by validating every step through the lens of test automation. It is a process and philosophy wrapped into a methodology — agreeing to embark on a journey where the finer-grained detail emerges from the work itself. Used inside-out (innermost core classes first, then downstream classes), with git checkpoints and interactive rebasing to correct deep mistakes and replay each class's tests forward. Rodzik's earlier example shows that naive red-green TDD with conditional tests can still yield green-but-wrong suites, reinforcing that the mechanics alone are not TDD.

category
methodology
about
Test Driven Development concept
Fredo begins by writing RSpec tests first and labels his approach TDD.
about
Test Driven Development concept
Major thread of the talk: TDD as process/philosophy, the V1 rewrite done under strict TDD.
about
Test Driven Development concept
Reframes TDD away from red-green-refactor mechanics.
about
Test Driven Development concept
Scott ties event-driven architecture to TDD via testability/transparency and setup-code quality signal.
about
Test Driven Development concept
Reframes TDD as being about setup minimization, not assertion syntax.
about
Test Driven Development concept
Argues TDD was never truly adopted in Rails because controllers weren't testable, and that applying TDD would have prevented the fat-model pattern.
about
Test Driven Development concept
Blimke recommends WebMock for TDD — define the expected HTTP behavior in the test first, worry about the HTTP client library later.
person Nathan Ladd
recommends
Test Driven Development concept
Advocates TDD as a process/philosophy for improving implementation quality.

Provenance

Read by
7 extractions