Skip to content

Releases: jdi-testing/jdi-light

1.4.7

04 Jan 16:43
29f4718
Compare
Choose a tag to compare
  • Fixed Firefox run
  • Cucumber version is updated to the latest 7.10.1

1.4.6

28 Oct 03:08
f6c6b3e
Compare
Choose a tag to compare
  • Selenium version is updated to version 4.4.0
  • WebDriverManager is updated to the latest 5.3.0
  • Opera is not supported anymore (Selenium stops supporting it)

1.4.5

22 Oct 01:53
b48a63f
Compare
Choose a tag to compare
  1. WebDriver download is fixed by checking that that driver is really downloaded
  2. UiElement.press is fixed for headless mode
  3. WindowsManager.getWindowsNames is added

1.4.4 Replace Log4J in jdi-light to Slf4j

18 Jan 20:23
28aef23
Compare
Choose a tag to compare
  • Remove log4j dependency from jdi-light (now only slf4j)
  • Update Allure version to 2.17.2

IMPORTANT: in order to have logs now you need to add log4j or any other logger (e.g. logback) in your pom directly
Logback example:

<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>${logger.version}</version>
</dependency>

Log4J example:

<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-api</artifactId>
    <version>${logger.version}</version>
</dependency>
<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-core</artifactId>
    <version>${logger.version}</version>
</dependency>
<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-slf4j-impl</artifactId>
    <version>${logger.version}</version>
</dependency>
<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-1.2-api</artifactId>
    <version>${logger.version}</version>
</dependency>

1.4.3 Add new loggers

15 Jan 22:09
49e6300
Compare
Choose a tag to compare
  • Refactored JdiLogManager
  • Add new loggers in addition to Log4JLogger: Slf4JLogger and ConsoleLogger
  • Slf4JLogger now default logger (because of log4j vulnerabilities) - this switch should not require any changes in code in the test projects
  • You can set new logger with:
    JdiLogManager.setLogger("My Awesome logger", new Slf4JLogger("JDI"));
    or add one more logger (stream) using:
    JdiLogManager.addLogger("My Awesome logger", new Slf4JLogger("JDI"));
    You can create your own logger by implementing interface IJDILogger
    Or fully replace jdi logger with new logger by implementing interface ILogger and set your logger to
    WebSettings.logger = new AwesomeLogger();

1.4.1 (1.3.23) Add Default settings for pages checks

04 Jan 17:28
c238c15
Compare
Choose a tag to compare

Added settings for default behavior while page.checkOpened() - method called
in test.properties:
page.check.url = contains
page.check.title = none

in code:
JDISettings.PAGE.checkUrlType = "match"
JDISettings.PAGE.checkTitleType = "equals"

Note: behavior for each page can be specified with @url / @title annotations

1.4.0 Selenium 4

30 Dec 10:57
2a36db1
Compare
Choose a tag to compare

JDI Light with Selenium 4

1.3.22 Security update: Log 4J version 2.17.0

20 Dec 13:28
2a36db1
Compare
Choose a tag to compare

Change version of Log4J to 2.17.0 Cause global vulnerability of lower versions

1.3.21 [dont use it] Accidently has low version of log4j

20 Dec 13:27
2a36db1
Compare
Choose a tag to compare
Selenium4 (#3628)

* update version

* switch to selenium 4.1

* switch to selenium 4.1

* switch to selenium 4.1

* update log4j to 2.17.0

* update over packages

* update mobile to selenium 3

* update mobile to selenium 3

* update mobile to selenium 3

* update to 1.3.22

* update mobile tests to 1.3.22

1.3.20 Security update

15 Dec 08:08
49a20b5
Compare
Choose a tag to compare