/cucumber-testng-testmarking

Primary LanguageHTML

Logo

BrowserStack Examples Cucumber TestNG Cucumber TestNG

Introduction

TestNG is a testing framework designed to simplify a broad range of testing needs, from unit testing (testing a class in isolation of the others) to integration testing (testing entire systems made of several classes, several packages and even several external frameworks, such as application servers). Cucumber is a software tool that supports behavior-driven development (BDD).

This BrowserStack Example repository demonstrates a Selenium test framework written in Cucumber and TestNG with parallel testing capabilties. The Selenium test scripts are written for the open source BrowserStack Demo web application (Github). This BrowserStack Demo App is an e-commerce web application which showcases multiple real-world user scenarios, written in Next and React. The app is bundled with offers data, orders data and products data that contains everything you need to start using the app and run tests out-of-the-box.

The Selenium tests are run on different platforms like on-prem, docker and BrowserStack using various run configurations and test capabilities.

Repository setup

  • Clone the repository

  • For this infrastructure configuration (i.e on-premise) ensure that the ChromeDriver executable is placed in the /src/test/resources/ folder.

  • Ensure you have the following dependencies installed on the machine

    • Java >= 8
    • Maven >= 3.1+
    • Gradle >= 5.0+

    Maven:

    mvn install

    Gradle:

    gradle build

About the tests in this repository

This repository contains the following Selenium tests:

Module Test name Description
E2E End to End Scenario This test scenario verifies successful product purchase lifecycle end-to-end. It demonstrates the Page Object Model design pattern and is also the default test executed in all the single test run profiles.
Login Login with given username This test verifies the login workflow with different types of valid login users.
Login Login as Locked User This test verifies the login workflow error for a locked user.
Offers Offers for Mumbai location This test mocks the GPS location for Mumbai and verifies that the product offers applicable for the Mumbai location are shown.
Product Apply Apple Vendor Filter This test verifies that 9 Apple products are only shown if the Apple vendor filter option is applied.
Product Apply Lowest to Highest Order By This test verifies that the product prices are in ascending order when the product sort "Lowest to Highest" is applied.
User Login as User with no image loaded This test verifies that the product images load for user: "image_not_loading_user" on the e-commerce application. Since the images do not load, the test case assertion fails.
User Login as User with existing Orders This test verifies that existing orders are shown for user: "existing_orders_user"

Test infrastructure environments

Configuring the maximum parallel test threads for this repository

For all the parallel run configuration profiles, you can configure the maximum parallel test threads by changing the settings below.

Test Reporting

On Premise / Self Hosted

This infrastructure points to running the tests on your own machine using a browser (e.g. Chrome) using the browser's driver executables (e.g. ChromeDriver for Chrome). Selenium enables this functionality using WebDriver for many popular browsers.

Prerequisites

  • For this infrastructure configuration (i.e on-premise) ensure that the ChromeDriver executable is placed in the /src/test/resources/ folder.

Note: The ChromeDriver version must match the Chrome browser version on your machine.

Running Your Tests

Run a specific test on your own machine

  • How to run the test?

    To run the default test scenario (e.g. End to End Scenario) on your own machine, use the following command:

    Maven:

    mvn test -P on-prem

    Gradle:

    gradle on-prem

    To run a specific test scenario, use the following command with the additional 'test-name' argument:

    Maven:

    mvn test -P on-prem -Dtest-name="<Test scenario name>"

    Gradle:

    gradle on-prem -Dtest-name="<Test scenario name>"

    where, the argument 'test-name' can be any Cucumber scenario name configured in this repository.

    E.g. "Login as username", "Login as Locked User", "Offers for mumbai geo-location" or any of the other test scenario names, as outlined in About the tests in this repository section.

  • Output

    This run profile executes a specific test scenario on a single browser instance on your own machine.

Run the entire test suite on your own machine

  • How to run the test?

    To run the entire test suite on your own machine, use the following command:

    Maven:

    mvn test -P on-prem-suite

    Gradle:

    gradle on-prem-suite

  • Output

    This run profile executes the entire test suite sequentially on a single browser, on your own machine.

Docker

Docker is an open source platform that provides the ability to package and test applications in an isolated environment called containers.

Prerequisites

  • Install and start Docker.
  • Note: Docker should be running on the test machine. Ensure Docker Compose is installed as well.
  • Run docker-compose pull from the current directory of the repository.

Running Your Tests

Run a specific test on the docker infrastructure

  • How to run the test?

    • Start the Docker by running the following command:
    docker-compose up -d
    • To run the default test scenario (e.g. End to End Scenario) on your own machine, use the following command:

    Maven:

    mvn test -P docker

    Gradle:

    gradle docker

    To run a specific test scenario, use the following command with the additional 'test-name' argument:

    Maven:

    mvn test -P docker -Dtest-name="<Test scenario name>"

    Gradle:

    gradle docker -Dtest-name="<Test scenario name>"

    where, the argument 'test-name' can be any Cucumber scenario name configured in this repository.

    E.g. "Login as username", "Login as Locked User", "Offers for mumbai geo-location" or any of the other test scenario names, as outlined in About the tests in this repository section.

  • After tests are complete, you can stop the Docker by running the following command:

    docker-compose down

  • Output

    This run profile executes a specific test scenario on a single browser deployed on a docker image.

Run the entire test suite in parallel using Docker

  • How to run the test?

    • Start the docker image first by running the following command:
    docker-compose up -d
    • To run the entire test suite in parallel on the docker image, use the following command:

    Maven:

    mvn test -P docker-parallel

    Gradle:

    gradle docker-parallel
    • After the tests are complete stop the Selenium grid by running the following command:
    docker-compose down

  • Output

    This run profile executes the entire test suite in parallel on a single browser, deployed on a docker image.

  • Note: By default, this execution would run maximum 5 test threads in parallel on Docker. Refer to the section "Configuring the maximum parallel test threads for this repository" for updating the parallel thread count based on your requirements.

BrowserStack

BrowserStack provides instant access to 2,000+ real mobile devices and browsers on a highly reliable cloud infrastructure that effortlessly scales as testing needs grow.

Prerequisites

  • Create a new BrowserStack account or use an existing one.

  • Identify your BrowserStack username and access key from the BrowserStack Automate Dashboard and export them as environment variables using the below commands.

    • For *nix based and Mac machines:
    export BROWSERSTACK_USERNAME=<browserstack-username> &&
export BROWSERSTACK_ACCESS_KEY=<browserstack-access-key>
    • For Windows:
    set BROWSERSTACK_USERNAME=<browserstack-username>
set BROWSERSTACK_ACCESS_KEY=<browserstack-access-key>

    Alternatively, you can also hardcode username and access_key objects in the bs.json file.

Note:

  • We have configured a list of test capabilities in the bs.json file. You can certainly update them based on your device / browser test requirements.
  • The exact test capability values can be easily identified using the Browserstack Capability Generator

Running Your Tests

Run a specific test on BrowserStack

In this section, we will run a single test on Chrome browser on Browserstack. To change test capabilities for this configuration, please refer to the single object in bs.json file.

  • How to run the test?

    • To run the default test scenario (e.g. End to End Scenario) on your own machine, use the following command:

    Maven:

    mvn test -P bstack-single

    Gradle:

    gradle bstack-single

    To run a specific test scenario, use the following command with the additional 'test-name' argument: Maven:

    mvn test -P bstack-single -Dtest-name="<Test scenario name>"

    Gradle:

    gradle bstack-single -Dtest-name="<Test scenario name>"

    where, the argument 'test-name' can be any Cucumber scenario name configured in this repository.

    E.g. "Login as username", "Login as Locked User", "Offers for mumbai geo-location" or any of the other test scenario names, as outlined in About the tests in this repository section.

  • Output

    This run profile executes a single test on a single browser on BrowserStack. Please refer to your BrowserStack dashboard for test results.

Run the entire test suite in parallel on a single BrowserStack browser

In this section, we will run the tests in parallel on a single browser on Browserstack. Refer to single object in bs.json file to change test capabilities for this configuration.

  • How to run the test?

    To run the entire test suite in parallel on a single BrowserStack browser, use the following command:

    Maven:

    mvn test -P bstack-parallel

    Gradle:

    gradle bstack-parallel

  • Output

    This run profile executes the entire test suite in parallel on a single BrowserStack browser. Please refer to your BrowserStack dashboard for test results.

Run the entire test suite in parallel on multiple BrowserStack browsers

In this section, we will run the tests in parallel on multiple browsers on Browserstack. Refer to the parallel object in bs.json file to change test capabilities for this configuration.

  • How to run the test?

    To run the entire test suite in parallel on multiple BrowserStack browsers, use the following command:

    Maven:

    mvn test -P bstack-parallel-browsers

    Gradle:

    gradle bstack-parallel-browsers

[Web application hosted on internal environment] Running your tests on BrowserStack using BrowserStackLocal

Prerequisites

  • Clone the BrowserStack demo application repository.

    git clone https://github.com/browserstack/browserstack-demo-app

  • Please follow the README.md on the BrowserStack demo application repository to install and start the dev server on localhost.

  • In this section, we will run a single test case to test the BrowserStack Demo app hosted on your local machine i.e. localhost. Refer to the single_local object in bs.json file to change test capabilities for this configuration.

  • Note: You may need to provide additional BrowserStackLocal arguments to successfully connect your localhost environment with BrowserStack infrastructure. (e.g if you are behind firewalls, proxy or VPN).

  • Further details for successfully creating a BrowserStackLocal connection can be found here:

[Web application hosted on internal environment] Run a specific test on BrowserStack using BrowserStackLocal

  • How to run the test?

    • To run the default test scenario (e.g. End to End Scenario) on a single BrowserStack browser using BrowserStackLocal, use the following command:

    Maven:

    mvn test -P bstack-local

    Gradle:

    gradle bstack-local

    To run a specific test scenario, use the following command with the additional test-name argument: Maven:

    mvn test -P bstack-local -Dtest-name="<Test scenario name>"

    Gradle:

    gradle bstack-local -Dtest-name="<Test scenario name>"

    where, the argument 'test-name' can be any Cucumber scenario name configured in this repository.

    E.g. "Login as username", "Login as Locked User", "Offers for mumbai geo-location" or any of the other test scenario names, as outlined in About the tests in this repository section.

  • Output

    This run profile executes a single test on an internally hosted web application on a single browser on BrowserStack. Please refer to your BrowserStack dashboard(https://automate.browserstack.com/) for test results.

[Web application hosted on internal environment] Run the entire test suite in parallel on a single BrowserStack browser using BrowserStackLocal

In this section, we will run the test cases to test the internally hosted website in parallel on a single browser on Browserstack. Refer to the single_local object in bs.json file to change test capabilities for this configuration.

  • How to run the test?

    To run the entire test suite in parallel on a single BrowserStack browser using BrowserStackLocal, use the following command: Maven:

    mvn test -P bstack-local-parallel

    Gradle:

    gradle bstack-local-parallel

  • Output

    This run profile executes the entire test suite on an internally hosted web application on a single browser on BrowserStack. Please refer to your BrowserStack dashboard for test results.

  • Note: By default, this execution would run maximum 5 test threads in parallel on BrowserStack. Refer to the section "Configuring the maximum parallel test threads for this repository" for updating the parallel thread count based on your requirements.

[Web application hosted on internal environment] Run the entire test suite in parallel on multiple BrowserStack browser using BrowserStackLocal

In this section, we will run the test cases to test the internally hosted website in parallel on multiple browsers on Browserstack. Refer to the parallel_local object in bs.json file to change test capabilities for this configuration.

  • How to run the test?

    To run the entire test suite in parallel on a single BrowserStack browser using BrowserStackLocal, use the following command:

    Maven:

    mvn test -P bstack-local-parallel-browsers

    Gradle:

    gradle bstack-local-parallel-browsers

  • Output

    This run profile executes the entire test suite on an internally hosted web application on multiple browsers on BrowserStack. Please refer to your BrowserStack dashboard for test results.

  • Note: By default, this execution would run maximum 5 test threads in parallel on BrowserStack. Refer to the section "Configuring the maximum parallel test threads for this repository" for updating the parallel thread count based on your requirements.

Generating Allure Reports

In this section, we will generate and serve allure reports for maven test runs.

  • Generate Report using the following command: mvn io.qameta.allure:allure-maven:report
  • Serve the Allure report on a server: mvn io.qameta.allure:allure-maven:serve

Additional Resources

Open Issues

  • Parallel thread count is not working via gradle command line arguments & gradle profiles , the thread count can be updated directly from the testng runner file