Java + Junit + Cucumber + Selenium testing cases

This repo contains the Maven setup for Cucumber / Selenium, with Searching Google with Cheese as example code, which can be run on local or connect to remote SaucsLabs / TestingBot for cross browser testings. Also it can be configured in your CI server (i.e. Bamboo) for continuous testing. It helps to setup a BDD environment for User Acceptance tests.

This repo can be run on local Windows / Mac / Linux Platform, as long as you have Java/Maven setup correctly.

Install Java & Maven on your local machine

= To Run (Maven command line) =

Local machine with browser name (ie / chrome / firefox / safari)

• Test with Google Chrome (Mac / Windows for machineType):

> mvn test -DsiteUrl=http://www.google.com -DbrowserName="googlechrome" -DmachineType="mac"

• Test with Firefox (Mac / Windows for machineType):

> mvn test -DsiteUrl=http://www.google.com -DbrowserName="firefox" -DmachineType="mac"

• Test with IE (Windows Only):

> mvn test -DsiteUrl=http://www.google.com -DbrowserName="ie"

• Test with Safari (After install Safari extension, see /drivers/README.md):

> mvn test -DsiteUrl=http://www.google.com -DbrowserName="safari"

Remote Webdriver:

• Testingbot (You can pass through Bamboo build variable for api key)

> mvn test -DsiteUrl=http://www.google.com -DenvName="remote" -DremoteWebDriver="http://<testingbot api key>@hub.testingbot.com:4444/wd/hub"

• SauceLabs (You can pass through Bamboo build variable for api key)

> mvn test -DsiteUrl=http://www.google.com -DenvName="remote" -DremoteWebDriver="http://<saucelabs api key>@ondemand.saucelabs.com:80/wd/hub"

See README inside /drivers folder

Gherkin is the language that Cucumber understands. You can find more Gherin Syntax here: https://github.com/cucumber/cucumber/wiki/Gherkin

Selenium is an automated web browser testing. You can find some commonly used Selenium commands here: http://www.seleniumhq.org/docs/02_selenium_ide.jsp#commonly-used-selenium-commands

You can update the siteUrl in the pom.xml property (default is http://www.google.com for my example) for your application need, also you can pass in from command line

Create a feature file under src\test\resources\myproject (You can group your feature in same directory, i.e. homepage / contact / products etc)

1. Copy your story / feature description (ideally same as from Jira description, As a site user, I want to ...., So that ...)
2. Under Scenario Outline: will contain all the Given / When / Then Gherkin You can specify "" as parameter from Data Table.
3. Fill in the Data Table for parameters listed in your step 2

The Data Table (even only 1 row) can help you to change the data input in the future and easier to understand the feature testing data. I reserved the use of the PageType / ScreenSize defined in CommonStepDef, so we can have responsive testing ready.

4. Then run the mvn test, it will throw the exception of missing implementation, and it will print out the Java Selenium function you need to implement (for next step)

= Implement the missing Java Scenario Step = 5. Create a java file under src\test\java\myproject (same, you can group as folder as the structure of feature folder)

Copy printed function signatures from last step, and implement the selenium action you want to achieve.

To create a continuous testing plan, please follow the below steps:

1. Create Bamboo Plan
2. Configure Plan: Repository (your repo)
3. Configure Plan: Bamboo Variables (if you want different testing domain for this plan (for your app testing environment) i.e. siteUrl = http://www.google.com

To pass in testingbot / saucelabs api endpoint, i.e. saucelabs_endpoint = http://<secret from saucelabs>@ondemand.saucelabs.com:80/wd/hub)

4. Stages -> New Stage -> Add Task:

• Source Code Checkout (from your repo configured)

• To add Chrome Maven 3.x task: Goal: clean test -DbrowserName=googlechrome -DenvName=remote -DremoteWebDriver=${bamboo.saucelabs_endpoint} -DsiteUrl=${bamboo.siteUrl} -DappName="My Project"

Working sub directory: If you have your cucumber in sub folder of your repo, then enter the subfolder name here

5. Repeat Step 4 if you want to test against ie10 / ie9 / firefox / ipad / iphone. One task for one devices, which will run full set of the testing cases. Also you can disable a task from time to time.

6. (Optional) Configure Plan: Triggers Add Scheduled builds, Trigger Type with Scheduled daily Or you can set Trigger the build when changes are committed or polling the repo for changes. Whichever you best match your use case for continuous testing.