Behavior-Driven Development (BDD) is an Agile approach that mixes requirement gathering, documentation and acceptance testing. The idea is that you start by writing human-readable sentences that describe a feature of your application and how it should work. Then you implement this behavior in software. This description can produce automated tests that will verify that the feature is implemented correctly. On the testing side, BDD tools provide you the features to perform functional or acceptance tests. There are many tools that implement the BDD concept for different languages, including PHP.
Behavior-Driven Development (BDD) tutorials
This presentation shows what it is like working with Behavior Driven Development (BDD) frameworks like JBehave, Cucumber or Concordian. It proposes an effective alternative solution for BDD which is ‘Spock’ – a convenient, lightweight framework, based on the Groovy language.
Gherkin is the language that many Behavior-Driven Development open source software testing tools like Cucumber or Behat use to define test cases. Gherkin is designed to be non-technical and human readable, and collectively describes use cases relating to a software system.
Behavior-Driven Development (BDD) is an Agile approach that mixes requirement gathering, documentation and acceptance testing. You write human-readable sentences describing the features of your application and how they should work. Then you implement this behavior using a tool that produces automated acceptance tests to verify that the feature is implemented correctly. Open source .NET BDD tools like SpecFlow are used to store the requirements as live documentation and to perform functional or acceptance tests.
There is a lot of talk in modern software testing teams about experimentation. Classically an experiment is a very structured series of activities designed to find something out. Sounds a lot like software testing and is in direct alignment with the concepts around Test-Driven Development (TDD), Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD). This video discusses how to design testing experiments that are valuable and provide the right insights to the right people, at the right time.
Even if Windows might be the most used operating system in software development organizations, it doesn’t mean that you cannot use a computer working with Mac OS to perform functional testing. This article provides a list of open source functional testing tools that work on Mac OS.
When you use a Behavior Driven Development (BDD) approach, you are going to automated tests for Agile user stories base on acceptance criteria. Defining these acceptance criteria between the product owner, the developers and the software testers is not always an easy task and can create lengthy discussions. In his article, Matt Wynne presents example mapping as a new approach to define acceptance criteria.