
Install IntelliJ IDEA to work with Cucumber and Selenium, selecting the free community version and preparing your editor for Selenium projects.
Create your first cucumber and selenium project by cloning a ready base from GitHub into IntelliJ, then explore feature files, step definitions, and pom.xml dependencies to start immediately.
Review the project dependencies in the XML file, including Selenium and Cucumber for Java with their versions, and prepare to write the feature file and step definitions for execution.
Install the cucumber plugin in IntelliJ IDEA to streamline working with cucumber, enable keyword recognition, and autofill, then restart the IDE to enjoy a cleaner editor view.
Explore Cucumber and Gherkin syntax as a business-friendly interface between testing teams and product teams, using given when then to translate requirements into automated actions.
Explore writing a Cucumber feature file using Gherkin syntax with given, when, and then steps to model login flows, validate actions, and identify driver setup issues.
Install and locate the Chrome driver for Selenium in Windows, download the correct version, and place it where Selenium can access it.
Write the first step definition snippet using cucumber and selenium with Java to map given when then steps to login actions and driver setup.
Resolve a given step definition error in Cucumber and Selenium with Java by defining steps, using driver.get to open Swag Labs, and wiring feature file steps to Java code.
Resolve the when step definition by creating or locating the set definition, then write a click action with Selenium to press the login button using a locator, confirming error resolution.
Create and verify the then step for login with Cucumber and Selenium. Use class name locators and expected conditions to confirm the username is required message appears and test passes.
Learn how to use Cucumber before and after hooks to set up the driver, close the browser after each execution, and manage memory during scenario runs.
Learn to pass parameters in cucumber by creating a parameterized scenario and step definition to navigate to a given website using driver.get with an http URL.
Use the background keyword in Cucumber to centralize setup steps that run before every scenario, such as opening the home page and initializing the web browser in Java with Selenium.
Learn how to run multiple data inputs in cucumber using a scenario outline and examples to test login, purchase, and checkout flows across different data sets.
Explore testing with Cucumber using a scenario outline and examples, wiring step definitions to username and password fields using Selenium with Java.
Reinforce how Cucumber uses scenario outlines with data sets to write automated test cases, and preview Selenium as the web driver for web automation.
Set up the Selenium web driver by configuring the Chrome driver path, creating a Chrome driver instance, and noting options for Edge, Firefox, or Safari; then navigate to a URL.
Learn to use the web driver to visit a URL with driver.get, passing addresses like linkedin.com or google.com, and wait for the page to load before interaction.
Locate web page elements with selenium’s driver.findElement using id, class name, name, link text, css selector, or tag name to support clicking or typing interactions.
Learn how to locate elements with Selenium, then interact with them using click, send keys, and clear actions, and verify results in Selenium tests.
Learn how to verify web page elements with Selenium using methods like displayed, enabled, and equals checks, ensuring buttons reflect user inputs and tests stop on failures.
Use driver.quit to close the browser and end the driver session after an automation task. In cucumber, compare driver.quit with driver.close to distinguish closing a page from terminating the session.
Learn in this course about Cucumber and Selenium. The powerful tools for test automation.
Complete course to get you started. All the tools used are free source. 24 lectures with examples. Fully coverage of all aspects of the subject.
What's cucumber?
Cucumber is a tool that supports Behaviour-Driven Development(BDD). If you’re new to Behaviour-Driven Development read our BDD introduction first.
What is Gherkin?
Gherkin is a set of grammar rules that makes plain text structured enough for Cucumber to understand. The scenario above is written in Gherkin.
What are Step Definitions?
Step definitions connect Gherkin steps to programming code. A step definition carries out the action that should be performed by the step. So step definitions hard-wire the specification to the implementation.
What's Selenium?
Selenium automates browsers.
What you do with that power is entirely up to you.
Primarily it is for automating web applications for testing purposes, but is certainly not limited to just that.
Boring web-based administration tasks can (and should) also be automated as well.
What is Automation Testing?
Automation Testing is a software testing technique that performs using special automated testing software tools to execute a test case suite. On the contrary, Manual Testing is performed by a human sitting in front of a computer carefully executing the test steps.