Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/neonidian/selenium-java-bdd-tests
Gherkin style BDD tests using Selenium and Java
https://github.com/neonidian/selenium-java-bdd-tests
bdd bdd-gherkin gradle java selenium selenium-bdd-java-template selenium-java test-automation testng testng-bdd webdriver
Last synced: about 1 month ago
JSON representation
Gherkin style BDD tests using Selenium and Java
- Host: GitHub
- URL: https://github.com/neonidian/selenium-java-bdd-tests
- Owner: neonidian
- License: mit
- Created: 2021-01-23T18:31:21.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-05-14T13:19:44.000Z (over 2 years ago)
- Last Synced: 2024-10-22T17:34:51.575Z (3 months ago)
- Topics: bdd, bdd-gherkin, gradle, java, selenium, selenium-bdd-java-template, selenium-java, test-automation, testng, testng-bdd, webdriver
- Language: Java
- Homepage:
- Size: 131 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Selenium with Java and BDD on Mitigram website
Mitigram is a digital platform for trade financing. More info at https://mitigram.com/
## Overview
* The repository contains browser based regression tests written in **Ghekrin style(Given-When-Then) using Cucumber Java library**
* The Gherkin style feature tests are located at [src/test/resources/com/mitigram/web/features](src/test/resources/com/mitigram/web/features)
* Pre-requisites to run the tests: Chrome browser, JDK installed
* To execute all the tests, open commandline -> go to this directory -> run `./gradlew`(Linux or Mac OS) or `gradlew`(Windows OS)
* After running the tests, the generated test reports can be viewed at [build/reports/tests/test/index.html](build/reports/tests/test/index.html)
and Cucumber generated test reports can be viewed at [build/cucumber-reports](build/cucumber-reports)
## Priority of regression tests
* The priority of the regression tests in this repository are based on the critical functionalities(which I think) of the application
* Based on the criticality, they have been classified as 'high' or 'low' priority using Cucumber tags and these tags used
in TestNG suite XML configuration
* 'high' priority tests defined in this repository means that these tests test the critical flow of the application
and _must_ pass as part of quality check
* 'low' priority tests defined in this repository means that these tests test functionality that are 'good to have' but
may not block a release
### Running high priority tests
To run only _high_ priority tests use the command use the Gradle task `highPriorityRegressionTests`
E.g., In Linux or Mac, open command-line and use this command
```console
./gradlew highPriorityRegressionTests
```
### Running low priority tests
To run only _low_ priority tests use the command use the Gradle task `lowPriorityRegressionTests`
E.g.,
In Linux or Mac, open command-line and use this command
```console
./gradlew lowPriorityRegressionTests
```
For Windows, open command-line like powershell and use this command
```console
gradlew lowPriorityRegressionTests
```
## Build system, libraries used
* Gradle is used as the build system. Build file - [build.gradle](build.gradle)
* TestNG library is used as the test library because it provides better way of handling parallel execution, order of execution
* TestNG suite XML configuration located at [src/test/resources/com/mitigram/web/testngrunners](src/test/resources/com/mitigram/web/testngrunners)
files have been used in the [build.gradle](build.gradle) file to run tests based on priority
* Cucumber library is used for writing BDD style specification tests
* Selenium library is used for browser based automation
* Webdrivermanager library is used for managing Selenium driver executables for various browsers
* Hamcrest is used as the assertion library
* Apache Commons configuration is used to retrieve configuration. Currently, only type of browser can be configured
through [src/test/resources/com/mitigram/web/browser.properties](src/test/resources/com/mitigram/web/browser.properties) file. This library can be further used
to use system properties, XML configuration and more when needed
## Test framework
* Page object model is used
* The [pages package](src/test/java/com/mitigram/web/pages) defines the functionality to be performed in a web page
* The [framework package](src/test/java/com/mitigram/web/framework) defines the Selenium based framework to perform actions in the browser
* The [regressiontests package](src/test/java/com/mitigram/web/regressiontests) provides the glue code for Cucumber tests based on priority
## Browsers supported
* Chrome, Firefox, Edge browsers are supported
* The browser can be configured through browser.properties located at
[src/test/resources/com/mitigram/web/browser.properties](src/test/resources/com/mitigram/web/browser.properties) file
## Running tests in IDE
To run tests in any Java based IDE,
1. Make sure TestNG IDE plugin is installed(mostly IDEs have this plugin by default)
2. Go to the glue code [directory](src/test/java/com/mitigram/web/regressiontests)
3. Right-click the file you would like to run based on priority and select a context action
which says like _Run tests_