Behaviour Driven Development (BDD) with Cucumber
Practical BDD: business analysis, development and test automation in one
Enroll immediately
More and more software development teams are adopting agile ways of working. In this context, it’s crucial to develop clear specifications and tests more quickly and effectively. BDD (Behavior Driven Development) supports teams in this process. BDD is a shift-left approach in which business stakeholders/analysts, testers, and developers collaboratively define specifications/requirements in their domain-specific language based on User Stories. Through this collaboration and the use of examples, a shared understanding is created. The resulting specifications/requirements also serve as executable tests. These tests can then be directly automated using tools like Cucumber.
Example of a BDD feature / scenario
Using Java/Cucumber
The test-first approach ensures that tests are written first—by business stakeholders/analysts, testers, anddevelopers in their domain-specific language—before any code is written. The final system must meet these predefined tests, which must be executed successfully.
This shared understanding ensures that everyone—business stakeholders/analysts, testers, and developers—clearly knows what a User Story must fulfill. Thanks to the test-first approach, the exact specifications/requirements are known to all parties in advance.
Topics covered during this training are:
Describing the expected behaviour of the system
Applying Gherkin scenarios (given ..., when ..., then ...).
Automating Gherkin scenarios.
Who is this training for?
This two-day course is designed for analysts, developers and testers. Prior knowledge required for this course is that the participant must be able to write basic Java and/or C# code.
What to expect.
You will learn where BDD supports and provides direction in analyzing requirements and how this analysis parallels the writing of test scripts
You will learn the ideas behind and the practical benefits and pitfalls of the Three Amigos and we will go very hands-on with writing good Gherkin / Feature files that you can use immediately in practice
You will learn how to keep documentation "living" and learn to automate both Feature Files and Scenarios with Java/Cucumber and/or C#/SpecFlow
Enroll
