This article is the last part of the BDD series: gathering all information

Behavioral Driven Development (BDD) is a software development approach that has evolved from TDD (Test Driven Development). It differs by being written in a shared language, which improves communication between tech and non-tech teams and stakeholders. In both development approaches, tests are written ahead of the code, but in BDD, tests are more user-focused and based on the system’s behaviour.

Below are links in alphabetical order:

  1. Behavior Driven Development Vol. 1
  2. Behavior Driven Development Vol. 2
  3. Behavior Driven Development Vol. 3

TDD works satisfactorily, as long as the business owner is familiar with the unit test framework being used and their technical skills are strong enough, which is not always the case. In these circumstances, BDD has the advantage because the test cases can be written in a common language used by the stakeholders such as for example, English. This access to clearer, low-jargon communication is probably the biggest advantage to using BDD, making it possible for collaboration between the technical and non-technical teams to run with improved efficiency.

This series of articles linked above can help with writing a well-tested code with business requirements.


Reference:

  1. Behavior Driven Development Vol. 1
  2. Behavior Driven Development Vol. 2
  3. Behavior Driven Development Vol. 3
  4. https://thatoneprivacysite.net

My site is free of ads and trackers. Was this post helpful to you? Why not BuyMeACoffee