New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support running environments sequentially #1901
Comments
Yes, but you can already do this by creating a small script which does something like |
Good point. We do something like that in ensemble. One downside is that this approach can be pretty verbose and repetitive, especially if the For example, it ends up being:
whereas something like this would be nice:
That can still be scripted, and that's what we do in ensemble, but a |
Would be nice to have because then the end user would get a nice summary of results at the end, compared to however many summaries displayed throughout the execution. |
+1 to this funcionality! |
I forgot to mention this earlier, but Even then, npm-run-all requires one script for each command that should be run sequentially, so you end up needing to provide one script for each invocation of the nightwatch command, which gets really verbose. We have this problem in mozilla/ensemble. |
+1 To get this! |
This has been discussed before (#138) but I'd like to formally request the feature.
Nightwatch can run tests in multiple environments simultaneously. For example, the following command will run all tests in Firefox, Chrome, and Safari at the same time.
nightwatch --env firefox,chrome,safari
There are times when running tests sequentially is preferable: first in Firefox, then in Chrome, then in Safari. For example, the most basic BrowserStack Automate plan only allows tests to be run in one browser at a time. I'd like to request that Nightwatch support this with a
--sequential
flag (or similar).The text was updated successfully, but these errors were encountered: