Why should I add another layer to make testing even more complicated?

Behavior Driven Development (BDD) is a popular software development methodology. BDD is an extension of Test Driven Development (TDD) inspired by Agile practices. But is the added layer really worth it? The primary reason to choose BDD as your development process is to break down communication barriers between business and technical teams. BDD encourages automated testing to verify all documented features of a project from the beginning.

Narrow the idea of story BDD:
* describe features in a scenario with a formal text
* use examples to make abstract things concrete
* implement each step of a scenario for testing
* write actual code implementing the feature

By writing every feature in User Story format that is automatically executable as a test, we ensure that: businesses, developers, QAs, and managers are all on the same page. BDD encourages exploration and debate to formalize the requirements and features by writing the User Stories so everyone can understand. By making tests part of the User Story, BDD allows non-technical personnel to write (or edit) Acceptance tests. This procedure also ensures that everyone in a team knows what was developed, what was not, what was tested, and what was not.

If you write your tests in a reusable way, it can often make your tests LESS complicated. Codeception collects and shares best practices and solutions for testing PHP web applications. With a flexible set of included modules, tests are easy to write, use, and maintain. Get started today writing your first BDD test.


Comments are closed.