Support for running tests in parallel about grunt-casper HOT 4 CLOSED

Hey Matt,

How are you intending on running the task?

I have started implementing a parallel task option with timing but want to make sure I cover your use case before pushing it to the 1.1 branch.

I.E.

casper : {
options : {
parallel : true,
concurrency : 10
},
files : /* Hash / Array ? */
}

from grunt-casper.

Yeah something like that. Max concurrency is a good idea. Does it wait until one of the first 10 tests is done, then start test #11, etc.?

Here's what ours looks like (right now we have a bunch of component tests and one big golden path test that looks at navigation between components):

casper : {
options : {

    test : true,

    includes: 'app/shared/test/setup.js',

parallel : true,
},
{

files : "app/entertainment/*/.test.js
}

One of the things we also wanted to look at is spinning up a separate node instance for each component test. That can probably happen down the line though when we have hundreds of them.

-- Matt Savino

(w) 310-964-4127
(c) 310-344-0889
IM: [email protected]

From: Chris Miller <[email protected]mailto:[email protected]>
Reply-To: iamchrismiller/grunt-casper <[email protected]mailto:[email protected]>
Date: Tuesday, October 22, 2013 12:49 AM
To: iamchrismiller/grunt-casper <[email protected]mailto:[email protected]>
Cc: DIRECTV <[email protected]mailto:[email protected]>
Subject: Re: [grunt-casper] Support for running tests in parallel (#14)

Hey Matt,

How are you intending on running the task?

I have started implementing a parallel task option with timing but want to make sure I cover your use case before pushing it to the 1.1 branch.

I.E.

casper : {
options : {
parallel : true,
concurrency : 10
},
files : /* Hash / Array ? */
}

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-26783265.

from grunt-casper.

Straight From Async Docs :

The same as each only no more than "limit" iterators will be simultaneously running at any time.

Note that the items are not processed in batches, so there is no guarantee that the first "limit" iterator functions will complete before any others are started.

I am close to having this finished.. I will complete it tonight after work.

from grunt-casper.

I pushed the fix to 1.1.. I was feeling ambitious. Let me know how it works for you.

Concurrency is maxed at 10 because of possible memory leaks in Node.

from grunt-casper.