Skip to content

Add workaround for selenium version 4 #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 21, 2022
Merged

Add workaround for selenium version 4 #128

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cc7979c
Add workaround for selenium version 4
dkrn03 Apr 14, 2022
bdefc84
apply retest ci
dkrn03 Apr 14, 2022
b47acee
apply recheck cli for key words
dkrn03 Apr 14, 2022
eed9534
Update formating
martin-v Apr 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
89 changes: 86 additions & 3 deletions docs/recheck-web/setup/maven.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ With this, you can now turn to your favorite IDE (e.g. `mvn eclipse:eclipse`) an

Extract the archive to your hard drive. Note that for the ChromeDriver to work, you need the major version to match your Chrome version installed on your system. Now we should be all set up to create [your first test](../tutorial/explicit-checks.md).

## Using ReTest in connection with Spring
If you plan to use Spring alongside with ReTest in the same project, you should know the following:
## Using ***recheck*** in connection with Spring
If you plan to use Spring alongside with ***recheck*** in the same project, you should know the following:

Since Java version 11 `javax.xml.bind` is replaced by `jakarta.xml.bind`. ReTest already uses the newer version, meaningly `jakarta.xml.bind`, while
Since Java version 11 `javax.xml.bind` is replaced by `jakarta.xml.bind`. ***recheck*** already uses the newer version, meaningly `jakarta.xml.bind`, while
Spring is still using `javax.xml.bind`. To avoid any errors, it is necessary to add the following dependencies to your `pom.xml` file.

```xml
Expand Down Expand Up @@ -90,3 +90,86 @@ Spring is still using `javax.xml.bind`. To avoid any errors, it is necessary to
<scope>test</scope>
</dependency>
```

Furthermore, Spring defines Selenium version 3 in its POM file whereas ***recheck*** (version >= 1.13) is using Selenium version 4.
The respective dependencies must therefore be overwritten in your `pom.xml` file by adding the following block.

```xml
<dependencyManagement>
<dependencies>
<!-- START workaround selenium 4 -->
<!-- recheck >= 1.13 uses selenium 4, spring defines selenium 3 in parent-pom, so we need to overwrite it. -->
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-api</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-chrome-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-devtools-v85</artifactId>
<version>4.1.2</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-devtools-v97</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-devtools-v98</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-devtools-v99</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-edge-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-firefox-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-ie-driver</artifactId>
<version>4.1.2</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-opera-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-remote-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-safari-driver</artifactId>
<version>[4,4.99)</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-support</artifactId>
<version>[4,4.99)</version>
</dependency>
<!-- END workaround selenium 4 -->
</dependencies>
</dependencyManagement>
```