Cucumber BDD Masterclass with Selenium 4 & Java + Framework

Learn why behavior driven development emerged from the waterfall model, where requirements lead teams through design, implementation, testing, and deployment.

Explain agile software development as an umbrella of frameworks, including Scrum, extreme programming, Kanban, and BDD, and how it addresses waterfall problems through iterative, collaborative, and flexible delivery.

Explore behavior driven development and its roots in test driven development, and learn to write failing unit tests, implement minimal code, and refactor to prevent defects in agile teams.

Understand how readable unit tests spark the birth of behavior driven development, when test names express business language and specification from tests.

Master BDD with Cucumber by exploring agile collaboration, given when then, acceptance criteria, executable specifications, and living documentation that stays in sync with the code.

Discover how behavior driven development and test driven development fit into agile processes. See BDD discovery, formulation, and automation with user stories and acceptance criteria in scrum iterations.

Master discovery, formulation, and automation in BDD through collaborative workshops, example mapping, and executable gherkin specifications that guide development and align stakeholders.

Hold a discovery workshop before starting a user story to clarify problems, capture details, and adapt plans, with the three amigos and 3–6 attendees using example mapping in bdd.

Learn example mapping for discovery workshops, using yellow story cards, blue rules, green examples, and red questions to focus on the smallest pieces of behavior.

Clarify BDD myths and align practice with collaboration through Cucumber as a BDD tool, not a requirement; emphasize discovery workshops and writing Gherkin collaboratively, with automation driving development.

Explore a full-fledged e-commerce site to practice Selenium automation, including navigating header, categories, search, filters, cart, checkout, and API-driven account creation.

Explore practical website testing for checkout flows with cucumber bdd, selenium 4 and java, covering shipping and tax rules, coupons, dummy data, and parallel automation scenarios.

Explore alternate practice websites for automation, including source demo, automation practice, and a bookstore with APIs, to validate front-end interactions, cart flows, and Selenium element handling.

Explore live example mapping to define user stories, acceptance criteria, and cucumber-based automation for add-to-cart scenarios, using Miro templates and concrete examples to clarify scope before development.

Set up a cucumber project in IntelliJ with a Maven build using JDK 17, add cucumber for Java and Gherkin plugins, and declare dependencies in pom.xml.

Set up a cucumber project in eclipse with maven, install the cucumber eclipse plugin, configure pom.xml with cucumber-java, create a gherkin feature, and run it to verify pending steps.

Demonstrate how Gherkin, a business readable domain specific language, describes system behavior in plain English and uses given, when, then to create executable specifications and project documentation.

Learn how the feature keyword in Gherkin provides a high level description of a software feature, including name, description, scenarios, background, and tags.

A scenario is an example illustrating a business situation and the system's behavior, serving as an executable specification for business stakeholders, with 5–8 steps using given, when, then, and, but.

Learn how Cucumber executes step sequences using given, when, then keywords, with regex-based matching to shared step definitions; keywords are immaterial, enabling reuse across scenarios.

Learn how given establishes the initial context, when performs an action, and then verifies observable outcomes, using and, but, and optional asterisk for lists.

Avoid step anti-patterns in Cucumber BDD by modeling system context, not user interface actions, and use api-driven state setup. Keep scenarios concise with observable outcomes for business readers.

Explore scenario outline to run a single scenario with different values using parameterized steps and examples, enabling data-driven testing with Cucumber and Gherkin.

Discover the rule keyword in Gherkin, introduced in Cucumber v6 and available for Cucumber JVM, to encapsulate a business rule and group multiple scenarios within a feature.

Use the background keyword to share common context across multiple scenarios by moving incidental given steps into a background. Execute the background before each scenario to improve readability and reuse.

Keep the background section concise and business-focused, including only user actions. Avoid technical steps and place them in hooks; limit to four steps to maintain readability and reduce maintenance.

Learn to craft gherkin scenarios that reflect the business requirements rather than implementation details, avoid tying scenarios to UI steps, and validate cart behavior while spotting common antipatterns.

Remove incidental details to keep the scenario focused on the store page, validating functionality over UI text and navigation, creating simple, deterministic cucumber tests.

Avoid multiple intentions in a single cucumber scenario; maintain one starting point and one ending point, focus on adding a product to the cart and conducting end-page assertions.

Keep cucumber BDD scenarios concise by limiting to 5-8 steps and splitting longer cases into multiple scenarios to preserve readability and expressive value.

Learn how conjunction steps enable reusing steps across scenarios in cucumber bdd, by writing generic steps like 'I am on the homepage' instead of highly contextual single steps.

Craft crisp, readable feature and scenario names in cucumber bdd, and clearly name rules and narratives. Use narration and user stories to convey validation without exposing how it’s tested.

Avoid anti-patterns in Cucumber and Gherkin to reduce maintenance, promote reusable steps, and improve scenario readability for collaboration between developers, business analysts, and product owners.

refactor the Gherkin into a concise, reusable store page scenario with a cart add action and a parameterized, data-driven outline for testing.

Learn how to drive cucumber scenarios with CLI, JUnit, or TestNG, using before/after class annotations, and understand parallel execution and portability implications.

Install Maven on Windows by downloading the Apache Maven zip, unzip, locate the bin folder, add its path to system environment variables, and verify with mvn command.

Execute cucumber scenarios from the command line using a java command or the maven plugin, configuring classpath, feature files, and glue code in the src test package for successful runs.

Learn to run Cucumber tests with JUnit four by configuring dependencies, setting up a JUnit runner, and aligning feature files with glue code under the same package for Maven tests.

Learn how to execute Cucumber scenarios using TestNG as the runner, configure cucumber testing dependency, and avoid JUnit conflicts in Maven projects to run tests with mvn clean test.

Explore using JUnit annotations with cucumber to set up and clean up test environments with before class and after class, and note portability when running via Maven versus CLI.

Use test annotations like before class and after class with Cucumber to set up the test environment and clean up databases, while considering portability across runners.

Master Cucumber 7 hooks before all and after all, including the static keyword, and see how they run with CLI, Maven, and JUnit/TestNG across different test scenarios.

Explore cucumber options and how to supply system properties and plugins via annotations across editors, JUnit, Maven, and CLI runners, with a look at configuration and the properties list.

Configure cucumber options to supply pretty and HTML formatter plugins, revealing scenario details. Run tests with testng or junit to generate the cucumber.html report in the target folder.

Learn how Cucumber generates code snippets for missing step definitions with underscores by default, and switch to camel case using the summary plugin and the snippets option.

Use dry run in cucumber to verify that all feature file steps have corresponding definitions without executing them, ideal for hundreds of scenarios; learn to set dryrun true and override with maven.

Enable monochrome to format the console output in a readable, black-and-white style, displaying scenario information in white. Try setting monochrome to true for the test runner and Maven command.

Organize runners, hooks, and step definitions in separate packages and configure glue and feature paths with cucumber options, ensuring before all and after all hooks run when dryrun is disabled.

Access javadocs and explore cucumber sources directly in the editor to learn tag expressions, constants, and available options by downloading sources and inspecting the library code.