You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were experiencing a problem for a while now where the driver was complaining about not being able to find the msedge binary. I am not entirely sure with which driver/browser version it started, but at least for v122 I can confirm that the setting browserName to "MicrosoftEdge" fixes the problem.
Here is the error message I got from karma before:
I think the problem is at the location linked below and it might be just a matter of changing the browser name there. I would have opened a PR, but I am not sure and can not verify if a change like that would break older versions.
We were experiencing a problem for a while now where the driver was complaining about not being able to find the
msedge
binary. I am not entirely sure with which driver/browser version it started, but at least for v122 I can confirm that the settingbrowserName
to "MicrosoftEdge" fixes the problem.Here is the error message I got from karma before:
Here is the configuration that we are using right now, which overwrites the browser name and seems to fix the issue:
I think the problem is at the location linked below and it might be just a matter of changing the browser name there. I would have opened a PR, but I am not sure and can not verify if a change like that would break older versions.
karma-local-wd-launcher/index.js
Lines 333 to 337 in d6a9fbb
The text was updated successfully, but these errors were encountered: