Skip to content
May 31, 2013 / selenium34

Parallel Running

Well, that sure was a silly mistake. We had overwritten the default gradle test task in our build file. That caused the maxParallelForks property to be ignored… Once we returned back to the default test task we were in business.

Prior to that, we were simply iterating over each of the different drivers in our Geb Configuration in our test step. Now we simply call each of those custom tasks in one line or we run multiple test  steps.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: