Master Cucumber BDD with Selenium: Frameworks from Scratch

Download and install the Oracle JDK on Windows using the 64-bit installer, then set the environment PATH and verify with java -version.

Learn to download and install the Java JDK on Mac from Oracle, selecting the correct dmg installer for your Mac, running the installer, and verifying with java -version.

check if maven is installed on mac with mvn -version and install if not, via homebrew or manual download from apache maven, then verify with mvn -version.

install and set up apache maven on windows 11. download the maven 3.9.1 binary zip, extract it, add the bin path to system variables, and verify with mvn --version.

Set up a fresh maven project in IntelliJ for cucumber BDD, add cucumber core, cucumber junit or testing, and reporting in pom.xml, then reload to resolve dependencies and run tests.

Write your first cucumber feature file, build step definitions, and run tests with a cucumber runner in a maven project. Organize resources and features under test resources and glue code.

Execute your first cucumber test by wiring a feature file, step definitions, and a test runner, then run via Marvin or Maven to verify two tests: valid and invalid login.

Create a cucumber feature file and step definitions to test login with a valid email and password, wire up a runner, and run the tests with Maven, Jenkins, or Marvin.

Set up cucumber with selenium in a live project by adding selenium dependencies to pom.xml and resolving Maven. Run cucumber-based tests to validate login for valid and invalid credentials.

Launch a Selenium test by creating a WebDriver, navigate to the login URL, enter credentials, submit, and verify login with the current URL using step definitions.

Execute a cucumber BDD workflow to run selenium tests and configure Safari remote automation. Learn teardown with before/after hooks and handle pass or fail outcomes in selenium with cucumber.

Learn how to use scenario outline to parameterize login tests in Cucumber BDD. Replace hard coded data with examples to pass username and password from properties or feature files.

Explore how to use scenario outlines to remove hard coding by passing data from examples. Validate multiple login outcomes and URL changes with a single scenario outline and result validations.

Master best practices for writing clear, readable Gherkin in Cucumber, emphasizing correct grammar and simple, single-flow scenarios. Collaborate with stakeholders to keep living documentation that supports automated tests.

Explore Cucumber tags to organize test execution by smoke, sanity, and regression, using feature or scenario level tags with and, or, not, and the tags option.

Learn how to configure and run cucumber bdd scenarios using tags, such as smoke, sanity, and regression, by editing feature files and updating the test runner to execute tagged scenarios.

Learn how to use end and or tag operators in Cucumber to selectively run tests by categories like smoke, sanity, and regression, optimizing execution time.

Learn how to run negative test cases with cucumber tags by excluding regression, using not operator, and applying feature and scenario level markers (login, smoke, sanity) to control test execution.

Explore cucumber hooks for before and after scenario setup and teardown, including browser launch, url navigation, and before steps; apply simple, modular best practices.

Learn how cucumber hooks run code before and after each scenario or step, and implement a hooks class for setup and cleanup around a login feature.

Learn to run a cucumber test using a testing.xml file by creating testing.xml at the project root and executing with mvn clean test -D suiteXmlFile=testing.xml for ci/cd and jenkins.

learn to run cucumber tests using a testng.xml file to configure parallel execution, specify the runner, and execute with mvn clean test while tracking login tests, hooks, and reports.

Install Maven and set the path, then run tests from the terminal with mvn clean test using a test engine XML file.

Set up api testing with cucumber Rest Assured by configuring maven dependencies, creating an api.feature and step definitions, and validating a get user endpoint with status code 200.

Execute api tests using cucumber bdd shows building feature files and step definitions with rest assured, running tests tagged api, and verifying status codes and user data.

Learn to generate and view cucumber's built-in reports from the target folder, including cucumber reports JSON and emailable HTML, and compare with allure for richer insights.

Learn how Allure reports visualize Cucumber test results, configure dependencies and plugins in pom.xml, set up a runner file, run tests with Maven, and generate and serve the report.

Install the allure CLI on Mac, Linux, or Windows using homebrew, brew install allure, or scoop; verify the version and set the bin path when needed.