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

Running tests in parallel #53

Open
dorgan opened this issue Jan 20, 2014 · 6 comments
Open

Running tests in parallel #53

dorgan opened this issue Jan 20, 2014 · 6 comments

Comments

@dorgan
Copy link

dorgan commented Jan 20, 2014

If you have over 100 tests some of which take a couple of seconds to run because of call backs it would speed things up to be able to run tests in a multi threaded environment.

@DanKaplanSES
Copy link

Yes I would also like this feature. Though I think the title of this issue should start with the word "Running" instead of "Ruining".

Any advice on how to set this up? Perhaps there's a way to do this by passing PhantomJS parameters in?

@maboiteaspam
Copy link

@dorgan,

did you mean run multiple urls simultaneously, or several tests simultaneously within the same url ?
Case 1 could be done within the task, but it needs some deep refactoring in my mind.
Case 2 is to configure in your qunit bootstrap, there s some option about this, i let you dig the qunit documentation for exact reference.

@DanKaplanSES
Copy link

I don't know about @dorgan, but I meant Case 1. For case 2, I'll look at
the qunit documentation but I'm surprised it has a solution since I thought
that javascript is single threaded and all the tests are running on one
page.

On Tue, Mar 11, 2014 at 2:30 AM, Clément [email protected] wrote:

@dorgan https://github.com/dorgan,

did you mean run multiple urls simultaneously, or several tests
simultaneously within the same url ?
Case 1 could be done within the task, but it needs some deep refactoring
in my mind.
Case 2 is to configure in your qunit bootstrap, there s some option about
this, i let you dig the qunit documentation for exact reference.

Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-37276840
.

@dorgan
Copy link
Author

dorgan commented Mar 11, 2014

I meant Case 1 (Multiple URLs)

@maboiteaspam
Copy link

@dorgan,
ok, definitely it will break key things in the task
the phantomjs iteration => it spawns one process for each url, needs to start one process for all urls and fetch them all in one time. Phantomjs can definitely execute many urls simultaneously within the same process.
the bridge => may need to be improved to provide more information in order to replace the result in the correct place of the tree result
the reporter => should be rethink to be able to receive and display results from various urls consecutively

Let see what the maintainers will say about this, but big job.

Eventually, did you evaluate mocha as an alternative, i know they have some qunit style support, but i can t guarantee it will work, i never tried myself.
http://visionmedia.github.io/mocha/#qunit-interface

Also you would still need to find a task that run your tests in parallel.

But, if it reveals successful, it could avoid you a PR. Also mocha provides much more reporters out of box than qunit.

Can t help you much more as i don t face such problems myself.

@tieTYT, it is definitely a single threaded language.

@dorgan
Copy link
Author

dorgan commented Oct 4, 2015

Seems like this would be a good start. https://github.com/iammerrick/grunt-parallel

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

4 participants