Behavior-Driven Development (BDD)

Behavior-Driven Development (BDD) is the process that helps ProductOwners, SoftwareEngineers, QualityEngineers, and business reps achieve a shared understanding of software behavior.

• BDD uses the specification language Gherkin (which can be easily understood by Product Owners, Developers, QA Engineers, and anyone in the business) to define acceptance tests.
• These acceptance tests are captured in FeatureFiles
• The CucumberTool understands GherkinLanguage. It takes these FeatureFiles as inputs, and generates GlueCode so QualityEngineers can write automated tests that conform to a standard.

As a Developer codes a new user story, the QA engineer constructs automated tests for it. At first, those tests will fail. But as the Developer continues to code, he or she will know when the code is mature enough that it will be accepted by the business. This way, the Developer is less likely to deliver software that does not meet requirements.

Additional Resources

• Shift Left BDD (Context & Examples) v1.0 - 10 Apr 2020 - 18 slides (Ultranauts Only)

-- NicoleRadziwill - 13 Apr 2020