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
There's no way to run tests in parallel on different environments without explicitly listing all of them out with the --env arg. This can result in very long commands to run against a lot of device types or browser/os combos
Suggested solution
either allow a "parent" class in the config file with the environments as child classes, or allow wildcards for the --env argument. If I wanted to run on 10 different android devices on browserstack, I could name them in a way that would allow me to use "browsertack.android.*" instead of listing them out like "browserstack.android.s22, browserstack.android.pixel7, etc."
Alternatives / Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Description
There's no way to run tests in parallel on different environments without explicitly listing all of them out with the --env arg. This can result in very long commands to run against a lot of device types or browser/os combos
Suggested solution
either allow a "parent" class in the config file with the environments as child classes, or allow wildcards for the --env argument. If I wanted to run on 10 different android devices on browserstack, I could name them in a way that would allow me to use "browsertack.android.*" instead of listing them out like "browserstack.android.s22, browserstack.android.pixel7, etc."
Alternatives / Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: