BDD
Behaviour-driven development: describing software behaviour as readable Given-When-Then scenarios that product people and developers agree on, then automating them as tests.
In more detail
Keep scenarios about observable outcomes and let step definitions call the real application boundary. In .NET, Reqnroll runs them.
Related terms
- Gherkin — The plain-text language for BDD scenarios, using the keywords Feature, Scenario, Given, When and Then.
- Reqnroll — An open-source .NET tool that runs Gherkin BDD scenarios as tests with xUnit, NUnit or MSTest.
- step definition — The C# method that runs when a Gherkin step matches its pattern, connecting plain-language steps to real code.
Taught in
- Behavior-Driven Development with Reqnroll — Modern .NET Core, C# & Enterprise Microservices
- Testing In Sequential, Iterative And Agile Lifecycles — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Test First, DevOps And Shift Left — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- User Stories And Acceptance Criteria — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
References
- Cucumber: Behaviour-Driven Development
- Reqnroll documentation
- ISTQB Glossary: behavior-driven development
- ISTQB CTFL Syllabus v4.0.1, section 2.1.3