2023.01.17

Core

• Add logWarning method to BFLogger
• Moved most part of the StepLogger from Selenium to Core module so it can be used also in other modules

Selenium

• StepLogger extends now base class from Core module adding methods typical for Selenium (like saving screenshot)

2023.01.16

Core

• Added onSetupFailure and onTeardownFailure on ITestObserver to better handle these events

Selenium

• Refactored creating screenshots on fails depending of the stage of the test case (setup, test, teardown)
• Added StepLogger utility with some common cases to create Allure steps directly in the report

2023.01.03

Core

• Added colors to console logs depending of the log level.
• Support for some environments.csv file issues that were causing the entire test run to fail. Now they will be logged as errors on the console.

2022.12.29

Selenium:

• Fix starting default driver on first test case (removed start method execution from DriverManager constructor)

API:

• Support custom Rest Assured configs
• Renamed BasePageWebAPI to BaseEndpoint
• Removed getting default driver on creating BaseEnpoint object and start method execution from DriverManager

2022.12.28

Selenium

• Thread safe BasePage.getDriverWait()
• BasePage.getDriver() with custom options as parameter

Possible breaking changes:

• Selenium driver is no longer created instantly when new page object is created (removed getDriver() from BasePage constructor). It is still created on first use of getDriver() method. This change should not affect test case executions but it is important to notice it. In most cases driver will be created on URL open step in the test case or any other call to getDriver (like checking any object on the page).

2022.12.23

Selenium

• DriverManager refactored.
• Fixed issue on getDriver method with custom browser options as parameter

2022.12.22

Selenium

• CustomStrategy for JUnit

There is known issue related with running JUnit 5 + Selenium 4 test cases.
As a workaround MrChecker has now CustomStrategy class implementation which should let you run your test cases parallel without any issues.
In your test projects pom file you need to usefollowing junit parameters for custom strategy.

junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.mode.default=${parallel.mode.default}
junit.jupiter.execution.parallel.mode.classes.default=${parallel.mode.classes.default}
<!--This doesn't work for JUnit + Selenium 4-->
<!--junit.jupiter.execution.parallel.config.strategy=fixed-->
<!--junit.jupiter.execution.parallel.config.fixed.parallelism=${thread.count}-->
<!--Use CustomStrategy-->
junit.jupiter.execution.parallel.config.strategy=custom
junit.jupiter.execution.parallel.config.custom.class=com.capgemini.mrchecker.selenium.junit.CustomStrategy

Then you should be able to execute your tests parallel with fixed thread count using parameter (10 as example):
-Dthread.count=10

2022.12.19

Core

• Hidden debug log from io.netty

2022.12.16

Support for Selenium 4.7.2 🎉🥳

Selenium module updated to support the latest version of Selenium 4.
Mobile module updated to support the latest version of Appium (also based on the latest Selenium).

Backward compatibility of old Selenium 3 grids:
Since Selenium 4 renamed one of the desired capabilities ("version" -> "browserVersion"), you may run into some problems when trying to run tests written with the latest MrChecker (Selenium 4) on an older Selenium 3 grid environment.
If you face such a problem:
Could not start a new session. Response code 500. Message: Unable to create session from...
You can try to set a dedicated attribute to solve it:
-Dselenium3grid=true

Known issues:

• You may see exceptions from the netty http client in the console logs - this is debug output only. No impact on test execution.
  Reflective setAccessible(true) disabled
• You can see exceptions from the log4j logger - they come from the netty client trying to log some stuff. No impact on test execution.
  ERROR FileManager (logs/${ctx:threadName}_env.log) java.io.IOException: Nazwa pliku, nazwa katalogu lub składnia etykiety woluminu jest niepoprawna

We will try to fix these issues in future releases.

Bumped - before Selenium 4

Bumped all dependencies except those related with Selenium 4.
New common version for all modules based on release date.

Refactored Selenium module DriverManager.
Added methods to run browser with options defined for specific test.

Some possible breaking changes:

• deleted not used example module
• deleted Opera support (temporary until it will be supported in Selenium 4)
• deleted SoapMessageGenerator (used JEE libraries)