BDD
Writing Executable Specifications
Elisabeth Hendricksson stated at Turku Agile Day 2010 that “Specs is an abbreviation for speculations”. She is right, specs are often speculations. How can this be avoided? Execution of code doesn’t leave any room for speculation. If the specs can be executed, they aren’t speculations anymore.
Read More
Linking Requirement and Acceptance Tests
Acceptance tests and requirements are linked. You can’t have one without the other. The tests clarify and amplify the requirements. A test that fails shows that the system does not properly implement a requirement. A test that passes is a specification of how the system works.
Read More
From Requirements to Automated Tests and Back
Learn how software applications can be specified, continuously developed, tested and delivered and how testing supports the flow from requirements through to acceptable systems. In the Agile community, Acceptance-Test Driven Development (ATDD), Behaviour-Driven Development (BDD), Test-Driven Development (TDD) and Specification by Example are gaining greater acceptance as an effective approach to developing systems of high […]
Read More
Successful Feature Injection
Feature injection is a business analysis approach that focuses on business value, an approach similar to Behavior Driven Development (BDD). It transfers knowledge to the team about how the project can deliver value and what are the features needed to deliver that value. Examples are used to transfer this information to the team in the […]
Read More
RSpec Best Practices
This article presents the best practices of using RSpec, a Behavior-Driven Development (BDD) tool for Ruby programmers.
Read More
BDD to the Rescue
In this blog post, Mehdi Khalili explains that Behavior Driven Development can help you in more than one way. First and foremost it removes the ambiguity from the requirements, but taking it a step further could give you a lot of significant benefits.
Read More