Test Driven Development

Improving your software in short development cycles.
Contributed by

Toni Syvänen

Johan Bonneau

Published September 10, 2018
Collection
1

What Is Test Driven Development?

Test Driven Development (TDD) is a software development process that relies on the repetition of a very short development cycle. Requirements are turned into test cases, then the software is developed to pass the tests. In other words, it creates a safety net that serves to keep the developer's problems or bugs at bay while enabling the developer to refactor efficiently. This is opposed to software development that allows software to be added that is not proven to meet requirements.

Why Do Test Driven Development?

  • Allows developers to create smaller units of improvement as initially code should only aim to pass the tests.

  • Leads to more modular and flexible code as it will be developed in smaller independent units.

  • Generates faster feedback, for example by telling you whether your last change (or refactoring) has broken some previously working code.

  • Creates a detailed specification.

How to do Test Driven Development?

Further Information

Look at Test Driven Development

Links we love

Check out these great links which can help you dive a little deeper into running the Test Driven Development practice with your team, customers or stakeholders.

Ask Us Anything


Open Practice Library Logo
Open Practice Library

powered by

Open Innovation Labs Logo
Connect with our Community:
Except where noted, content on this site is licensed under a Creative Commons Attribution 4.0 International license.