Appium-cucumber : Automation Testing Using Java
Cucumber is a behavior driven development (BDD) approach to write automation test script to test Web and Mobile It enables you to write and execute automated acceptance/unit tests. It is cross-platform, open source and free. Automate your test cases with minimal coding.
Project-Name
|
|_src/main/java
| |_appUnderTest
| | |_calc.apk
| | |...
| |_browserConfigs
| | |_saucelab_windows_chrome.properties
| | |_browserstack_windows_chrome.properties
| | |...
| |_platformConfigs
| |_saucelab.properties
| |_browserstack.properties
| |...
|_src/main/resources
|_src/test/java
| |_env
| | |_DriverUtil.java
| | |_Hooks.java
| | |_RunCukeTest.java
| |_userStepDefinitions
| | |_loginSteps.java
| | |_signUpSteps.java
| | |...
|_src/test/resources
| |_features
| | |_login.feature
| | |_signUp.feature
- src/test/resources/features - all the cucumber features files (files .feature ext) goes here.
- src/test/java/userStepDefinition - you can define step defintion under this package for your feature steps.
- src/test/java/env - this package contains cucumber runner (RunCukeTest.java) where you can configure your glue code location (step defintions), define test result output format.(html, json, xml). Hooks where you can configure all before and after test settings Hooks.java, DriverUtil.java contains code for intializing driver instances for respective driver.
- src/main/java/platformConfigs - If you want to run your test on saucelab and browserstack platforms, you need to add its configuration such as username, access key here.
- src/main/java/browserConfig - When you run your test on remote browser/platform you have to provide capabilities and platform information here.
- src/main/java/appUnderTest - If you are testing mobile based application you can keep your app build here.
1. Feature File is an entry point to the Cucumber tests.
2. This is the file where you will describe your tests in Descriptive(Gherkin) language (like English).
3. It is an essential part of Cucumber, as it serves as an automation test script as well as the live document.
4. A single feature file can contain one or many scenarios
Feature: Defines what feature you will be testing in the tests below
Scenario: Defines the scenario that you will test
Given: Tells the pre-condition of the test
When: Defines the condition of the test
And: Defines additional conditions of the test
Then: States the postcondition. You can say that it is an expected result of the test.
A Step Definition is a java method in a class/file with an annotation(like: @Given, @When, @then, etc) attached to it, followed by the pattern(like: “^click on "([^"])"$”).
This pattern is used to link the Step Definition to all the matching (Gherkin)Steps => this code is what Cucumber would execute when it sees a Gherkin Step. Cucumber finds the Step Definition file with the help of Glue code in Cucumber Options.
This class will set up the interaction between the feature file and step definition file.
In layman language @CucumberOptions are like property files or settings for your test. @CucumberOptions enables us to do all the things that we could have done if we have used the cucumber command line.
This is very helpful and of utmost importance, if we are using IDE such as eclipse only to execute our project.
Parameterization in cucumber is basically done when you have the same scenario but few events are changing, to perform parameterization in cucumber, enter the keyword(event) in double-quotes.
Background Keyword is written at the very starting of the feature file, Any statement or group of statements added to the background will execute before the execution of all the scenarios mentioned in that feature file.
The cucumber features goes in the features library and should have the ".feature" extension.
You can start out by looking at features/my_first.feature. You can extend this feature or make your own features using some of the predefined steps that comes with selenium-cucumber.
By using predefined steps you can automate your test cases more quickly, more efficiently and without much coding.
The predefined steps are located here
Execution Flow:
Runner class >> Feature file >> Step Definition
Run the Test from the Runner.class. (Run as 'JUnit' or 'TestNG')
To run test on saucelab, browserstack or any other remote browser you need to create browser config file under src/main/java/browserConfig
To run on saucelab create config file with name preceding with saucelab
- saucelab_windows_chrome.properties
- saucelab_mac_firefox.properties
mvn test "-Dconfig=saucelab_mac_firefox"
To run on browserstack create config file with name preceding with browserstack
- browserstack_windows_chrome.properties
- browserstack_mac_firefox.properties
mvn test "-Dconfig=browserstack_mac_firefox"
Appium Desired Capabilities: https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/caps.md