2023.03.07

Selenium / Playwright

• Handle all throwable on BasicElement usability check

2023.03.06

Selenium/Playwright

• Romeved final from element types methods

Selenium

• ScrollUtils reworked

2023.03.03

Selenium & Playwright

• Element type interface

2023.02.27

Bump dependencies:
Maven surefire plugin 3.0.0-M8 -> M9
Selenium 4.8.0 -> 4.8.1

Selenium

• Rework element types

Playwright

• Add more element types

2023.02.08

Core

• Fixed typo in environments.csv file path
• Refactored to lazy loading environments.csv file

Playwright

• Adapted default LoadState in refresh or load page BasePage methods

Possible breaking changes

• Migrating to newest version require adapting the path of environments.csv file

2023.02.07

Handle new headless modes

Selenium

• Adapt "-Dheadless" parameter to support all new modes provided by Chromium browsers: https://www.selenium.dev/blog/2023/headless-is-going-away/

For Chromium browsers (Chrome, Edge) there are two kinds of headless mode - 'old' and 'new'.
You can use one of these parameters to work with one of them:

-Dheadless=false (don't add any browser arguments, it is default if parameter is not used)
-Dheadless=true (adds '--headless' argument to browser options, it is "old" headless mode)
-Dheadless=chrome (adds '--headless=chrome' argument to browser options, it is 'new' headless mode for versions 96-108)
-Dheadless=new (adds '--headless=new' argument to browser options, it is 'new' headless mode for versions 109+)

Firefox browser has one headless mode. You can use one of these parameters to work with it:

-Dheadless=false (don't add any browser arguments, it is default if parameter is not used)
-Dheadless=true (adds '-headless' argument to browser options, )

Playwright

Headless mode is also supported by Playwright. You can use one of these parameters to work with it:

-Dheadless=false (disables headless mode)
-Dheadless=true (enables headless mode, it is default if parameter is not used)

2023.02.06

Bump dependencies. List of most important changes:
Maven surefire plugin 3.0.0-M3 -> M8
JUnit 5.9.0 -> 5.9.2
JUnit Platform 1.9.0 -> 1.9.2
RestAssured 3.0.6 -> 5.3.0
AspectJ 1.9.9.1 -> 1.9.19
Playwright 1.28.1 -> 1.29.9
Selenium 4.7.2 -> 4.8.0

Selenium

• https://www.selenium.dev/blog/2023/selenium-4-8-0-released/
• Removed unused properties (for example for not supported Opera browser)
• Refactored setting browser options in DriverManager

2023.02.03

Selenium

• Don't add empty platform and browser version desired capabilities (fix some issues with connections to Selenium grid)

You don't longer need to use -Dselenium3grid=true for backward compatibility with Selenium 3 grids if you don't use -DbrowserVersion or -Dos on your commands.

2023.02.02 Playwright module

Playwright

• Initiation of new Playwright module with approach based on Selenium module

2023.01.27

Core

• Refactored TestExecutionObserver (handle more events properly)

Selenium

• Adapted to changes in Core (BasePage properly handles screenshots in events onTestExecutionException, onSetupFailure and on TeardownFailure to save screens at the time issue occur)

Default approach in MrChecker is still that tests from single class should be executed on single thread sequentially (JUnit 'same_thread' value in '' attribute). WebDriver is by default closed onTestClassFinish event.
There is an option to change this behavior - for example to run all tests from class parallel ('concurrent' as JUnit attribute value) or to use new browser for each test even executing them sequentially. Then you should execute DriverManager.closeDriver() on onTestFinish() event method on extended BasePage class.

public class BasePageGUI extends BasePage {
    @Override
    public void onTestFinish() {
        super.onTestFinish();
        DriverManager.closeDriver();
    }
}