[MGNLTEST-364] Improve/fix Selenium#newRemoteWebDriver to harmonize with SaasWebdriver for random selenium-ports Created: 25/Nov/22 Updated: 18/Dec/22 Resolved: 06/Dec/22 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Christoph Meier |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2.5h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Epic Link: | cucumber-and-selenide-support-by-test-fwk | ||||
| Work Started: | |||||
| Description |
|
In Selenium#newRemoteWebDriver, we assign the URL for the remoteWebdriver, before instantiating the WebDriver (which then gets wrapped with VaadinWebDriverWrapper). In SaasWebdriverConfiguration, we set (again!) remoteWebdriverUrl - for Selenide. org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
I know that the driverSetup looks complicated, IS complicated. How it can be fixed hopefully:In Selenium#newRemoteWebDriver, before assembling seleniumServerUrl: |