Chapter Summary

What You Learned

• BDD writes tests in plain English that the whole team can read — business, QA, and dev speak the same language.
• Gherkin syntax: Feature, Scenario, Given/When/Then, Background, Scenario Outline + Examples, @tags.
• Setup: cucumber-java + cucumber-testng dependencies, feature files in resources/features, step definitions in test/java.
• The runner class extends AbstractTestNGCucumberTests with @CucumberOptions for features, glue, plugins, and tags.
• Cucumber Expressions ({string}, {int}) are the modern way to capture parameters. Data Tables for structured data.
• Scenario Outline = one test, many data sets. The Cucumber equivalent of TestNG DataProvider.
• @Before/@After hooks manage browser lifecycle. scenario.attach() embeds screenshots in reports.
• Tags (@smoke, @regression) organize tests. Run selectively with -Dcucumber.filter.tags.
• Step definitions call page object methods — never put raw Selenium code in step definitions.
• Create separate runner classes for smoke, regression, and module-specific test suites.
• Masterthought cucumber-reporting generates rich HTML reports with embedded screenshots and environment metadata.

Cucumber BDD is a powerful layer on top of your TestNG + Selenium framework. It does not replace TestNG — it adds the ability to write tests in plain English that serve as living documentation. In the next chapters, we will build on this foundation with Page Object Model patterns and data-driven frameworks.