docs: update Selenium testing pages for Selenium 4 compatibility#5407
Merged
docs: update Selenium testing pages for Selenium 4 compatibility#5407
Conversation
The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358
Preview DeploymentThis PR has been deployed for preview. URL: https://docs-preview-pr-5407.fly.dev Built from 800c15a |
caalador
approved these changes
Mar 31, 2026
vaadin-bot
pushed a commit
that referenced
this pull request
Mar 31, 2026
The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358
vaadin-bot
pushed a commit
that referenced
this pull request
Mar 31, 2026
The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358
vaadin-bot
pushed a commit
that referenced
this pull request
Mar 31, 2026
The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358
mshabarov
pushed a commit
that referenced
this pull request
Mar 31, 2026
…) (#5420) The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358 Co-authored-by: Marco Collovati <marco@vaadin.com>
mshabarov
pushed a commit
that referenced
this pull request
Mar 31, 2026
…) (#5421) The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358 Co-authored-by: Marco Collovati <marco@vaadin.com>
mshabarov
pushed a commit
that referenced
this pull request
Mar 31, 2026
…) (#5422) The documentation recommended `WebDriverManager` (bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated. - Remove `WebDriverManager` dependency, imports, and setup calls - Explain that Selenium 4.6+ manages drivers automatically - Update Jetty plugin from 9.x to 12.1.7 with EE10 coordinates - Update `maven-failsafe-plugin` from 2.19.1/3.0.0-M7 to 3.5.5 - Fix outdated `<selenium.version>` property reference Fixes #5358 Co-authored-by: Marco Collovati <marco@vaadin.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The documentation recommended
WebDriverManager(bonigarcia) for driver management, but since Selenium 4.6 this is built-in via Selenium Manager. Also, several Maven plugin versions were outdated.WebDriverManagerdependency, imports, and setup callsmaven-failsafe-pluginfrom 2.19.1/3.0.0-M7 to 3.5.5<selenium.version>property referenceFixes #5358