https://github.com/hoangthach252/cucumber6-junit5-selenide-gradle

Sample Cucumber JVM6 Framework with Junit5 and Selenide
https://github.com/hoangthach252/cucumber6-junit5-selenide-gradle

allure-report assertj bdd-framework cucumber data-cleanup data-management gradle junit5 logback parallel-execution picocontainer selenide

Last synced: about 2 months ago
JSON representation

Sample Cucumber JVM6 Framework with Junit5 and Selenide

• Host: GitHub
• URL: https://github.com/hoangthach252/cucumber6-junit5-selenide-gradle
• Owner: hoangthach252
• Created: 2022-12-20T16:49:51.000Z (about 2 years ago)
• Default Branch: master
• Last Pushed: 2023-02-11T17:25:41.000Z (almost 2 years ago)
• Last Synced: 2024-01-26T02:31:08.682Z (11 months ago)
• Topics: allure-report, assertj, bdd-framework, cucumber, data-cleanup, data-management, gradle, junit5, logback, parallel-execution, picocontainer, selenide
• Language: Java
• Homepage:
• Size: 75.2 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Automation Framework using Cucumber JVM6 + JUnit5 + Selenide + Gradle + Allure + logback

A sample BDD Automation framework using Cucumber6, JUnit 5, Selenide, Gradle, Allure, logback.

Support running tests in parallel, sharing data among test steps and manage Page Objects using Dependency Injection.

Sample tests against [Unsplash](https://unsplash.com/) web app.

## Libraries Used

* [Junit](https://junit.org/junit5/docs/current/user-guide/) - 5.7.2

* [Gradle](https://gradle.org/guides) - 7.6

* [Cucumber](https://cucumber.io/docs/cucumber/) - 6.11.0

* [Selenide](https://selenide.org/documentation.html) - 5.24.0

* [Selenide wiki](https://github.com/selenide/selenide/wiki)

* [PicoContainer](https://github.com/cucumber/cucumber-jvm/tree/main/picocontainer) - 6.11.0

* [Allure](https://docs.qameta.io/allure/) - 2.14.0

* [Allure-Selenide](https://selenide.org/documentation/reports.html) - 2.14.0

* [Allure-Cucumber](https://docs.qameta.io/allure/#_cucumber_jvm) - 2.14.0

* [Logback](http://logback.qos.ch/manual/index.html) - 1.2.5

* [AssertJ](https://assertj.github.io/doc/) - 3.20.2

Reference Links:

* [cucumber-junit-platform-engine](https://github.com/cucumber/cucumber-jvm/tree/main/cucumber-junit-platform-engine)

## Run/Debug tests

* run all tests in parallel, number of threads can be specified in CukesTestRunner or junit-platform.properties or from command:

    $ gradlew -Dcucumber.execution.parallel.config.fixed.parallelism=3 clean test --info

* run all tests with specific tag.

    $ gradlew -Dcucumber.filter.tags=@id-002 clean test --info

* run all tests in `firefox` browser.

    $ gradlew -Dselenide.browser=firefox clean test --info

* Debug test on IntelliJ IDE.

Trigger Debug using CukesTestRunner.java.

After the tests are ran, you can see:

* logs from file appender under `build/logs/log.log`

* Allure results `build/allure-results`

## ScenarioContext

Represents test context to save/get test data and share it among test steps in one Cucumber scenario.

Example:



scenarioContext.setContext(DataItem.COLLECTION_NAME, collectionName);





String collectionName = (String) scenarioContext.getContext(DataItem.COLLECTION_NAME);



## DataStorage

Represents a storage to store test data and handle clean up after each Cucumber scenario.

Example:



dataStorage.setCollectionNames(collectionName);



## Allure reports

Allure report will contain framework logs, Selenide browser interaction logs, screenshots and page sources for

failing test cases

* [Allure CLI](https://docs.qameta.io/allure/#_commandline) should be installed

* Allure results stored in `build/allure-results`

* To generate allure report, first navigate to unsplash directory then run command:

    $ allure serve

## Logback configuration

You can find logback configuration here `src/test/resources/logback.xml`

Current configuration contains two appenders:

(default log level: INFO)

* ConsoleAppender will output logs to system out stream

* FileAppender will output logs to `build/logs/log.log`