Execution on SeleniumHQ Remote browser redirecting to a different than requested.

[sravan-jessu]

QAF Version

Note: only the latest version is supported.

Steps To Reproduce

1. Create a maven project, add required QMetry QAF and selenium-java (V4.2.2) dependencies. 
2. Create sample test to navigate any open public site
3. Start execution on Selenium HQ Chrome and Microsoft Edge Remote browsers. 

Expected behavior

When execution started with on Selenium HQ remote Microsoft Edge browser, test should start on the same browser.

Actual behavior

We are executing tests in selenium HQ with few capabilities, even though the capabilities are correct few times instead of selecting browser based on the capability's client send it is attempting the tests in a different browser. The actual capability after driver gets created are with a different browser than what client requested for.

The redirecting of browser is happening after connection to selenium hq is happened. So, we are thinking it's not our code issue. Same code works fine at times. but when we run multiple tests (capabilities client passes looks good) instead of desired browser other browser is being set for execution. And getting hung from there.

Is the issue reproducible on runner?

• [x] QAS
• [x] Maven
• [ ] Gradle
• [ ] Ant
• [x] Eclipse

Test case sample

we are seeing this behavior for any sample URL navigate case, so create a sample test to navigate and try to start test execution on Selenium HQ Chrome, Microsoft Edge remote browsers.

[sravan-jessu]

We have also observed this browser redirection issue with base quantum project. could someone assist with this issue?

[cjayswal]

Will you be able to provide everything that is necessary for someone else to reproduce the issue? Please refer http://sscce.org/