Skip to content
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

Closed
IgorMinar opened this issue Sep 18, 2012 · 1 comment
Closed

Don't synchronize test runs across multiple browsers #57

IgorMinar opened this issue Sep 18, 2012 · 1 comment
Milestone

Comments

@IgorMinar
Copy link
Contributor

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.

@chieffancypants
Copy link

+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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants