Understanding Test‑Driven Development: From TDD Mindset to Contract Testing and Standards

Readers familiar with agile will recognize Test‑Driven Development (TDD) as a concept that drives code creation through predefined test criteria; the author stresses that TDD should be viewed as a mindset rather than merely unit‑test‑driven development (UTDD).

Quoting Kent Beck, the origin of TDD is described as manually specifying expected output and iterating until the program matches, a practice that feels natural to seasoned programmers.

From this perspective, TDD is presented as an obvious way of working.

In practice, the TDD mindset can be applied across many stages of software development, and the author lists several concrete practices that embody this mindset.

Contract Testing is defined as a collaboration between consumer and provider based on a pre‑defined contract, aligning with TDD thinking by standardising expectations and avoiding mismatches caused by informal agreements.

Acceptance Criteria are highlighted as essential in agile teams; the "opening card" practice at ThoughtWorks requires developers to articulate their understanding of requirements against acceptance criteria before implementation, reducing deviation risk and embedding quality, while approaches like BDD also integrate criteria into development.

Standard‑Driven development extends the idea further: once standards are established, they drive team behaviour, though applying this in reality can be challenging.

The article identifies two major obstacles: how to create standards that achieve consensus and how to keep those standards up‑to‑date.

Teams often perceive standards as rigid constraints that increase workload, leading to resistance and a tendency to cling to existing habits.

To motivate adherence, the author suggests aligning standards with team or individual pain points and ensuring the outcomes of the standards gain collective agreement and recognition.

Ultimately, applying TDD requires understanding its mindset, selecting suitable scenarios, and adapting practices such as UTDD, ATDD, BDD, and others to the specific team context; the mindset remains the foundation for any agile practice.

The piece concludes with a promotion for the IDCF DevOps Hackathon, an end‑to‑end DevOps experience combining lean startup, agile development, and a CI/CD pipeline, scheduled for February 25‑26, 2023 in Hangzhou, inviting both corporate and individual participants.