Blog Watch

This project contains UI tests for baeldung.com

Overview

The project uses Selenium framework, Crawler4J, jsoup and REST Assured for UI tests . The tests can be run in GUI or headless mode. UI browser has been configured with Firefox using gecodriver and tested with Firefox 56.0 (64 bit) on Windows. Headless mode works with Chrome and HtmlUnit browsers.

Running Tests from the IDE

The default configuration executes tests with headless mode in windows environment and target URL is https://www.baeldung.com. The configuration can be changed using following properties:

• spring.profiles.active - environment variable to either "headless-browser" and "ui-browser"
• target.env - environment variable should be set to "win" or "linux" for headless browser
• base.url - to target base URL, for example http://www.baeldung.com

These can be set as environment variables via the Eclipse run configuration.

Running Tests Using Maven

Three Maven profiles are available for running tests:

• headless-browser-windows
• headless-browser-linux
• ui-brower-windows

The target URL for all profiles is https://www.baeldung.com. This can be changed using following property

• base.url - to target base URL, for example http://www.baeldung.com

Headless Browser selection

Available headless browsers

• HtmlUnit
• chrome-headless

Headless browser can be configured using following system property

• headless.browser.name

Updating List of Posts and Pages

Run UpdateArticlesAndPagesLinks#updateLinks test for updataing list of articles and pages.

JUnit Tags

Following tags are available for running tests selectively. Refer Java docs in GlobalConstants.java for details

• hourly
• daily
• weekly
• editorial
• github-related
• technical

Excluding a URL for tests running in the bi-monthly bild

URLs can be added to the following file to skip a specific test from the bi-monthly build - https://github.com/eugenp/blogwatch/blob/master/src/main/resources/exceptions-for-tests.yaml

Launch Mode

Set environment variable "LAUNCH_FLAG" to either true or false to set launch mode. Default is false

Execution Summary

After all the tests have finished, a test execution summary is logged, with the following format:

============================================================================
Test Execution Summary
============================================================================
Total Failures: X

Executed Tests: Y
testName_1(y1 executions)
testName_2(y2 executions)
...

Failed Tests: Z
failedTest_1(z1 failures)
failedTest_2(z2 failures)
...
=============================End of the Summary===============================

Test execution and test failure counts are automatically collected with the TestMetricsExtension.

For specific situation where this can not be used, we can explicitly collect these numbers inside the test, by invoking:

BaseTest.recordExecution("<TEST_NAME>");
BaseTest.recordFailure("<TEST_NAME>", <COUNT>);

Explicit invocation of these methods is needed in the following situations:

• the test is annotated with GlobalConstants.TAG_SKIP_METRICS
• we want to record multiple failures inside the same test
• the test is invoked from another test (eg: PagesUITest.givenTestsRelatedTechnicalArea_whenHittingAllPages_thenOK)

On Jenkins

The tests are running here, on Jenkins

Tests

https://docs.google.com/spreadsheets/d/18CcFYAjVmElakaFDzVgLxJ4pyjeKP09BSu9GqG_Uv9U