-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Don't synchronize test runs across multiple browsers #57
Labels
Milestone
Comments
+1 This would be particularly awesome for remote browsers (such as browserstack). They charge you for every second of use, and some browsers (older ones in particular) are queued and take several minutes before they are available. This means immediately available browsers will sit there eating time waiting for the queued browsers. |
pkozlowski-opensource
added a commit
to angular-ui/bootstrap
that referenced
this issue
Jan 8, 2014
Due to karma-runner/karma#57 moving to karma-runner 11 is a prerequisite before switching to SauceLabs testing
This was referenced Sep 27, 2018
This was referenced May 25, 2019
1 task
1 task
h918m
added a commit
to h918m/bootstrap
that referenced
this issue
Nov 28, 2021
Due to karma-runner/karma#57 moving to karma-runner 11 is a prerequisite before switching to SauceLabs testing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using testacular to launch browsers (via
browsers
option), testacular should start a test run as soon as individual browsers connect – currently testacular waits for all browsers to connect and only then it starts test runs in all the browsers.Similarly, when
singleRun
option is used, testacular should shut down browsers as they complete running tests. This will release OS resources speeding up the remaining browsers.The text was updated successfully, but these errors were encountered: