Closed maveric-systems closed 7 months ago
@maveric-systems it's not crashing. You are passing wrong capabilities.
No matching capabilities found
@maveric-systems it's not crashing. You are passing wrong capabilities.
No matching capabilities found
Thanks for your reply. Any help in identifying the issue will be appreciated... Edge browser is getting initiated, but the session is not getting established. Never had issue with other browser images.
Below config works for Chrome / Firefox for past 2 yrs: (Using Qmetry framework with TestNg)
driver.name=chromeRemoteDriver
remote.server=https://11.0.0.1:4444/wd/hub
chrome.capabilities.browserName=chrome
chrome.capabilities.browserVersion=96.0
chrome.capabilities.name=Test Pack 45 for Chrome
driver.additional.capabilities={'selenoid:options':{'sessionTimeout':'1m', 'enableVNC':true,'enableLog':true,'enableVideo':true,'videoName': '624cedf095e42647c24c05ef-Web - testpack.mp4','logName': '624cedf095e42647c24c05ef-Web - testpack.log'}}
Below config not working for Edge
driver.name=edgeRemoteDriver
remote.server=https://11.0.0.1:4444/wd/hub
chrome.capabilities.browserName=MicrosoftEdge
chrome.capabilities.browserVersion=99.0
chrome.capabilities.name=Test Pack 45
driver.additional.capabilities={'selenoid:options':{'sessionTimeout':'1m', 'enableVNC':true,'enableLog':true,'enableVideo':true,'videoName': '624cedf095e42647c24c05ef-Web - testpack.mp4','logName': '624cedf095e42647c24c05ef-Web - testpack.log'}}
@maveric-systems name
capability should also live under selenoid:options
as it is Selenoid specific.
I have identified the issue at last... "platformName" is mandatory for the Edge browser. It is not required for chrome, firefox, etc. As mentioned by @vania-pooh "name" can be outside or inside Selenoid Options.. Both are getting accepted.
// Is mandatory
edge.capabilities.platformName=ANY
BUG: Except for Curl, the Capabilities generator in Selenoid console is not mentioning platformName for Yaml, Java, C#, etc. Please fix the generator.
Thanks @vania-pooh for the prompt help you have provided. It made me to dig more into config. Please help how to create the bug.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
During the Automation run, Edge browser crashes. All other browsers are working fine like Chrome, Firefox, etc. Note: Manual creation of Edge session is working fine, only issue during Automation run
Edge version using: 99.0 & 89.0
Framework property file: (Note: Below config works for all other Browsers)
Docker Logs:
Browser.json Config
Automation Log: