Discussion:
[Cucumber] [JVM] Issue with executing cucumber features in parallel using selenium grid
(too old to reply)
Yogesh Aggarwal
2012-08-13 10:25:29 UTC
Permalink
Hi,

For Parallel execution of features on different systems using selenium
Grid, I executed the following two maven commands in background (on linux):

mvn clean verify -Dcucumber.filters="--tags @tags1" &
mvn clean verify -Dcucumber.filters="--tags @tags2" &

This will send the requests to grid in parallel. But grid is not able to
execute these tests in parallel. It executes one scenario on one machine
and then the other scenario on other machine. Also some tests gets fail
(not sure why). Seems to be some undesirable behaviour.

Does anyone know why grid is unable to execute the cucumber scenarios in
parallel in above case?

One thing to note is that: if we don't use selenium grid in the above
configuration, then the tests executes correctly in parallel on the local
machine by executing both of the above commands in background.

Thanks!
--
-- Rules --

1) Please prefix the subject with [Ruby], [JVM] or [JS].
2) Please use interleaved answers http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
3) If you have a question, don't reply to an existing message. Start a new topic instead.

You received this message because you are subscribed to the Google Groups Cukes group. To post to this group, send email to cukes-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org To unsubscribe from this group, send email to cukes+***@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/cukes?hl=en
Yogesh Aggarwal
2012-08-14 08:24:02 UTC
Permalink
Post by Yogesh Aggarwal
Hi,
For Parallel execution of features on different systems using selenium
This will send the requests to grid in parallel. But grid is not able to
execute these tests in parallel. It executes one scenario on one machine
and then the other scenario on other machine. Also some tests gets fail
(not sure why). Seems to be some undesirable behaviour.
Does anyone know why grid is unable to execute the cucumber scenarios in
parallel in above case?
One thing to note is that: if we don't use selenium grid in the above
configuration, then the tests executes correctly in parallel on the local
machine by executing both of the above commands in background.
Thanks!
Any ideas or thoughts on this?
--
-- Rules --

1) Please prefix the subject with [Ruby], [JVM] or [JS].
2) Please use interleaved answers http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
3) If you have a question, don't reply to an existing message. Start a new topic instead.

You received this message because you are subscribed to the Google Groups Cukes group. To post to this group, send email to cukes-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org To unsubscribe from this group, send email to cukes+***@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/cukes?hl=en
Rex Hoffman
2012-08-14 18:32:59 UTC
Permalink
Post by Yogesh Aggarwal
Hi,
For Parallel execution of features on different systems using selenium
This will send the requests to grid in parallel. But grid is not able to
execute these tests in parallel. It executes one scenario on one machine
and then the other scenario on other machine. Also some tests gets fail
(not sure why). Seems to be some undesirable behaviour.
Sounds like your grid is incorrectly set up. How many slave nodes, and
browser instances do you have? Where are the slave nodes being run? Have
you tested your grid configuration?
Post by Yogesh Aggarwal
Does anyone know why grid is unable to execute the cucumber scenarios in
parallel in above case?
I don't think this has anything to do with cucumber.
One thing to note is that: if we don't use selenium grid in the above
configuration, then the tests executes correctly in parallel on the local
machine by executing both of the above commands in background.
really sounds like your grid config.... was does your grid topology look
like? Have you hit up the selenium mailing list? You probably should get
your grid rock solid first, before putting cucumber on top of it?
Post by Yogesh Aggarwal
Thanks!
--
-- Rules --

1) Please prefix the subject with [Ruby], [JVM] or [JS].
2) Please use interleaved answers http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
3) If you have a question, don't reply to an existing message. Start a new topic instead.

You received this message because you are subscribed to the Google Groups Cukes group. To post to this group, send email to cukes-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org To unsubscribe from this group, send email to cukes+***@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/cukes?hl=en
Noodles
2018-07-16 16:54:06 UTC
Permalink
Hi Yogesh, is there a tutorial you know about on how I can set up parallel
testing with Selenium Grid?
Right now my framework has a driverFactory.java that returns one driver
instance.

Some say multiple runner classes, others using testng (but I do not know
how to integrate that with cucumber).
Others say using maven plugins.

I don't know how to begin getting this set up, can you advice?
Post by Yogesh Aggarwal
Hi,
For Parallel execution of features on different systems using selenium
This will send the requests to grid in parallel. But grid is not able to
execute these tests in parallel. It executes one scenario on one machine
and then the other scenario on other machine. Also some tests gets fail
(not sure why). Seems to be some undesirable behaviour.
Does anyone know why grid is unable to execute the cucumber scenarios in
parallel in above case?
One thing to note is that: if we don't use selenium grid in the above
configuration, then the tests executes correctly in parallel on the local
machine by executing both of the above commands in background.
Thanks!
--
Posting rules: http://cukes.info/posting-rules.html
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...