msedhu1007 / tojtech3 Goto Github PK

This is selenium based UI test automation framework for both member and recruiter sides.

1. Java - is used as the main coding language.
2. Maven - is used as build and dependencies management tool.
3. Chrome - Chrome browser.
4. ChromeDriver - standalone server for Chrome browser that implements the W3C WebDriver standard.

1. Docker - is used:
   1. spin up Selenoid - Selenium Grid
   2. executed tests

All the test framework related configs are stored in config.properties file. In order to overwrite default values either:

• Update the appropriate key in config.properties file.
• Pass the updated key as java environment variable into during tests run with maven. E.g. selenium.browser.isGrid=false is set to false in config.properties but during run on Jenkins we need to use selenium grid so that we are setting it to true by:

mvn clean install -Dselenium.browser.isGrid=true

There are 3 ways of tests execution: fully local, fully dockerized and mixed.

• Fully local is the preferred way during tests development as it simplifies debug process. It requires [Development Environment] environment setup because tests are executed (from IDE or using maven) against locally installed Chrome browser. As it's the default way of running tests (as per the configuration file) no additional parameters are required for running all the tests with maven:

mvn clean install

• Fully dockerized is the preferred way to execute tests as part of CI flow. See docker-compose.yml It requires [CI Environment] environment setup because tests are executed in docker containers. For the first run related docker containers should be pulled with:

docker pull selenoid/chrome:latest 
docker pull selenoid/opera:latest
docker-compose pull

In order to execute all the tests:

docker-compose down
docker-compose run tests mvn clean install -Dselenium.browser.isGrid=true -DparallelTestsCount=7
docker-compose down

• Mixed In order to execute tests from local environment using selenium grid. It requires both [Development Environment] and [CI Environment] setup. In order to run tests:

1. Selenium Grid should be started
2. Grid URL should be set in config.properties
3. isGrid flag should be set to true After that you will be able to execute tests in the same way as in [Fully local] case but the dockerized browsers will be used.

Generated reports are stored in the following locations:

• cucumber report: ui_tests/target/cucumber/index.html
• cucumber timeline report: ui_tests/target/cucumberTimeline/index.html The better implementation of reports is available on CI with cucumber-reports plugin.

Set selenium.browser.enableScreenShotsCapture flag to true in order to capture screenshots on open of page objects. They will be stored in: ui_tests/target/features folder

1. TestNG - tests execution and assertions.
2. Cucumber - behaviour driven development (BDD) support.
3. Selenium - browser interaction API.

1. If browser doesn't start:
   1. Check if version of chromedriver (chromedriver(.exe) -v in terminal) matches version of inatalled chrome browser
   2. Check if Glue is set to com.saucedemo in Run/Debug Configurations > Templates > Cucumber java > Glue line
2. Fully Dockerized execution on Windows platform is TBD. Please use Mixed approach.