Cucumber-JVM

Create Gherkin Feature File

• Add BDD feature & scenario data

Create Test Runner File

• glue = StepDefs
• DryRun=true
•  

Create StepDefs File under /StepDefs

• Add Step Definitions to code files under StepDefs
• Best to organize StepDefs into subfolders for 'feature', 'sprints', 'macros', navigation, testID
• Duplicate method names CAN NOT exist in this StepDefs package
  • So... BDD language should be carefully planned out for maximizing re-use & avoiding redundancy of actions
  • if 5 stepdefs are created for login and the login routine changes....
    • will have to update the same routine 5 times.
• Macros are helpful for multi-step routines that are commonly used across tests

Cucumber BDD - Page Object Model

• BaseClass
  • WebDriver
  • properties
• Loginpage.java extends BaseClass
  • WebElements
  • login()
    • return HomePageObject
• HomePage() extends BaseClass
  • WebElements
• Feature
• StepDefinitions
  • calls PageObjects
• TestRunner
  • conx with Feature & Definition
•  

@Before

public void setup(){}

@After

public void teardown(){}

Global

@Before()

@After()

Tagged Scenarios

@First

Scenario: first scenario

@Second

Scenario: second scenario

@Third

Scenario: third scenario

For @First ONLY ( NOT GLOBAL )

@Before("@First")

@After("@First")

Tagged Hooks

@Before() //Global

@Before("@First") //Specific

@After("@First") //Specific

@After() //Global

Ordered Hooks

@Before(order=0) //Global

@After(order=0) //Global

@Before(order=1) //Global

@After(order=1) //Global

Tags are just annotations that allow for grouping of feature tests

Feature

Feature: Deal data creation

Scenario: Free CRM Create a new deal scenario

    #Using a HashMap
    Given user is already on Login Page
    When title of login page is Free CRM
    Then user enters username and password
        | username | password |
        | naveenk | test@123 |
    Then user clicks on login button
    Then user is on home page
    Then user moves to new deal page
    Then user enters contact details
    #FORMAT = ctrl-shift-f
        | title      | amount | probability | commission |
        | test deal1 | 1000 | 50 | 10 |
        | test deal2 | 2000 | 60 | 20 |
        | test deal3 | 3000 | 70 | 30 |
    Then close the browser

Using DataTables isn't really preferred, but here's how to do it

Data Driven BDD

Then user enters username and password

    @Then("^user enters username and password$")
    public void user_enters_username_and_password() {
        driver.findElement(By.xpath("//input[@name='username']")).sendKeys("naveenk");
        driver.findElement(By.name("password")).sendKeys("test@123");
    }

Then user enters "naveenk" and "test@123"

//    @Then("^user enters \"(.*)\" and \"(.*)\"$")
    @Then("^user enters \"([^\"]*)\" and \"([^\"]*)\"$")
    public void user_enters_username_and_password(String username, String password) {
        driver.findElement(By.xpath("//input[@name='username']")).sendKeys(username);
        driver.findElement(By.name("password")).sendKeys(password);
    }

@WithExamples

Test Runner Cucumber Options

dryRun

true = Validate the Cucumber Feature, Definition & Runner wiring

false = execute Definition logic

Features

Glue

Tags