Don't synchronize test runs across multiple browsers

[IgorMinar]

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]

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