Open GoogleCodeExporter opened 9 years ago
Looking at the source code, I see the problem with this bit:
for (final Behavior behavior : behaviors) {
RunnableBehavior task = new RunnableBehavior(behavior);
executedBehaviors.add(task);
executor.execute(task);
}
executor.shutdown();
executor.awaitTermination(60, SECONDS);
Selenium tests can easily run longer than 60 seconds, so this timeout should be
configurable.
Original comment by lpiispa...@gmail.com
on 26 May 2011 at 8:59
Yep. agreed, what should the flag be?
Original comment by rich...@bluetrainsoftware.com
on 26 May 2011 at 10:19
Maybe "parallelTimeout" or something to that extent...?
Also, it would be very useful to be able to control the amount of parallel
threads. Currently I'm using a custom Semaphore mechanism to limit the number
of concurrent browser instances on our build server - it can't quite cope with
ten simultaneous Firefox instances. This flag could be "maxThreads" or
something?
Original comment by lpiispa...@gmail.com
on 26 May 2011 at 10:39
Sure. You building via maven or some other mechanism? I'm just concerned about
writing tests for this :-)
Original comment by rich...@bluetrainsoftware.com
on 27 May 2011 at 2:25
please review commit.
https://github.com/easyb/easyb-core/commit/686dbd16be137b42a6bc1a2c0109bf2922746
b2d
Original comment by richard....@gmail.com
on 27 May 2011 at 5:49
I added it into Ant as well.
Original comment by richard....@gmail.com
on 27 May 2011 at 6:09
Looks good to me! Will clone and test still.
Original comment by lpiispa...@gmail.com
on 27 May 2011 at 8:25
Original issue reported on code.google.com by
lpiispa...@gmail.com
on 26 May 2011 at 8:51