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

Add option to execute Browsers in serial instead of parallel #1465

Closed
ghost opened this issue Jun 23, 2015 · 4 comments · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed

Comments

@ghost
Copy link

ghost commented Jun 23, 2015

Can it change to run one by one?

thanks

@dignifiedquire
Copy link
Member

You can use a task runner like gulp or grunt to trigger different runs one after another by using different configurations.

@dignifiedquire
Copy link
Member

For questions and support please use the mailing list or Gitter. The issue tracker is for bug reports and feature discussions only.

@jokeyrhyme
Copy link

I'm having this problem as well. I'm using the following karma plugin to automatically launch browsers that are present without causing errors for missing browsers:

If every member of my team had all the same browsers installed, then it would be feasible to modify our grunt / gulp configuration to execute different nearly-identical configurations to get tests running in one browser at a time. Unfortunately, my team members are spread across Linux, Windows and OS X, so the only way to eliminate the automatic detection problem is to only ever test in PhantomJS, Chrome and Firefox and never test in Safari or Internet Explorer, or the various smartphone emulators.

So, automatic browser detection is necessary for my team, and this is not built-in to Karma: #1470.

The other problem my team has is that we do not all run the same hardware: some have more RAM, some have faster CPUs. Because of this, there is great variation in our ability to run tests in every single detected browser all at the same time. Even on the fastest machines we do not have a 100% pass rate (whilst we do when manually triggering the tests in one browser at a time).

Ultimately, the gulp / grunt suggestion here doesn't apply to our use case, so it would still be extremely helpful if karma has a built-in option to launch / capture browsers in serial instead of in parallel. I suspect this would help greatly with Travis CI as well.

@dignifiedquire dignifiedquire changed the title When use multi browser for e2e test, it take up too much cpu space. Add option to execute Browsers in serial instead of parallel Jul 29, 2015
@rshah88
Copy link

rshah88 commented Aug 31, 2015

This feature would also help in performance tests as currently when running performance tests.
Currently when I run the performance numbers with all browsers the numbers are 5-6 times compared to when the test is run on individual browser.

dignifiedquire added a commit to dignifiedquire/karma that referenced this issue Oct 21, 2015
Especially services like Browserstack and SauceLabs have limitations on
how many browsers
can be launched at the same time. The new config option `concurrency`
allows to
specify an upper limit of how many browsers are allowed to run at the
same time.

Ref: karma-runner/karma-sauce-launcher#40

Closes karma-runner#1465
dignifiedquire added a commit to dignifiedquire/karma that referenced this issue Oct 21, 2015
Especially services like Browserstack and SauceLabs have limitations on
how many browsers
can be launched at the same time. The new config option `concurrency`
allows to
specify an upper limit of how many browsers are allowed to run at the
same time.

Ref: karma-runner/karma-sauce-launcher#40

Closes karma-runner#1465
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants