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
I noted that Firefox testing does not work, at least on Browserstack, using mochify --wd, after version 58 (the last that works out of the box). No amount of fiddling with selenium or gecko driver versions helped.
Finally, what did work, is calling mochify with --async-polling false.
The issue now is that, with a .min-wd that starts multiple test runs (Chrome, Mac, Win, Firefox, Edge, Safari, mobiles, …), all test runs are executed with --async-polling false.
Is there a way to set this property only for some test runs, and not for others?
The text was updated successfully, but these errors were encountered:
Interesting case. This is currently not possible. A workaround would be to have multiple webdriver config files and run mochify multiple times, specifying the file with --wd-file <file>.
If you want this feature, I'm happy to help you implement it in min-webdriver as a new config field.
I noted that Firefox testing does not work, at least on Browserstack, using mochify --wd, after version 58 (the last that works out of the box). No amount of fiddling with selenium or gecko driver versions helped.
Finally, what did work, is calling mochify with --async-polling false.
The issue now is that, with a .min-wd that starts multiple test runs (Chrome, Mac, Win, Firefox, Edge, Safari, mobiles, …), all test runs are executed with --async-polling false.
Is there a way to set this property only for some test runs, and not for others?
The text was updated successfully, but these errors were encountered: