Hi Jay,
I am currently having the same problem, how did you solve yours?
Test execution is happening only in one node-chrome container. Also, I am
unable to connect over VNC to see what is happening inside
node-chrome-debug container and do you know anything about why is this
happening?
This is my multiCapabilities setup:
multiCapabilities: [
{
//shardTestFiles: true,
maxInstances: 5,
sequential: true,
browserName: 'chrome',
specs: ['tests/initial/*.spec.js']
},
],
Thank you,
Almeid
On Wednesday, January 27, 2016 at 4:51:53 AM UTC+1, Jay Perry wrote:
>
> Hi,
>
> Wanted to see if anyone was able to get selenium grid working with
> protractor so that you can run tests in parallel that are shared across the
> running selenium nodes?
>
> I found this writeup on how to setup selenium grid using docker containers
> and it's pretty easy and I have grid up and running. I was able to run
> protractor and point to it but the tests only seem to run on one of the
> node containers. I tried using the multiCapabilities and that didn't seem
> to solve it. Anyone else doing this?
>
> As for context, we have integration tests that use protractor-http-mock
> and we would like to spread these out over multiple browser sessions to
> have it run faster. Using the multiCapabilities is slight flaky and
> doesn't consistently run all the tests. Any suggestions?
>
> Thanks,
> Jay
>
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
