x Driven Development

x Driven Development

In traditional software development, code is first written, after which it is tested. The test execution and test coverage often get in trouble with the project planning. A "test first" approach can prevent this, because tests are set-up first and then developed. Such an approach is also called x Driven Development and there are different variants such as BDD, TDD and ATDD. Many organizations find it difficult to interpret the differences and similarities.

Test Driven Development (TDD)

TDD is a programming style that creates incremental unit tests and then writes code to make those tests succeed. TDD results in a set of automated unit tests. However, the purpose of TDD is to predetermine expectations.

Read more about this training here

Acceptance Test Driven Development (ATDD)

With ATDD, tests based on user stories are drawn up in an iterative way. User stories contain requirements and these requirements are elaborated in tests. The testing is done jointly by business, developers and testers before the code is developed. ATDD results in a set of acceptance tests. However, ATDD's goal is a shared understanding of the software to be built.

Read more about this training here

Behaviour Driven Development (BDD)

BDD is a method of developing software based on behavior. The behavior is described in a way that is understandable to team members by means of examples. Usually, Given-When-Then constructions are used. Cause and effect are used as a basis for setting up.

Read more about this training here