16

I have a single test which receives data from data provider. I would like this test to run in parallel with different values from data provider .

I tried an approach like :

public class IndependentTest { @Test(dataProvider = "dp1" ,threadPoolSize=3,invocationCount=1) public void testMethod(int number) { Long id = Thread.currentThread().getId(); System.out.println("HELLO : " + id); } @DataProvider(name = "dp1",parallel=true) public Object[][] dp1() { return new Object[][] { new Object[] { 1 }, new Object[] { 2 }, new Object[] { 3 }, new Object[] { 4 }, new Object[] { 5 }, new Object[] { 6 }, new Object[] { 7 }, new Object[] { 8 } }; } 

}

The output i received is :

HELLO : 10

HELLO : 12

HELLO : 17

HELLO : 11

HELLO : 16

HELLO : 14

HELLO : 13

HELLO : 15

Spawned 10 threads while i specified 5 in the thread pool size . Could you please tell what has to be added to the above snippet to control the data provider thread pool size .

3
  • You'll want to run tests in parallel, not the provider. In your build configure the parallel mode to methods and threadCount to 5. Commented Jul 20, 2015 at 16:43
  • hi Ben , I have a single test which is supposed to run more than 10k times based on the number of values provided by the data provider . I would like to control the number of threads spawned when parallel=true is set in dataprovider. I found this commandline argument -dataproviderthreadcount to control dataprovider thread count. However i would like to know how this could be done using annotations Commented Jul 20, 2015 at 17:41
  • In my project's build I configure tests to run in parallel and, in total, execute 1.8M due to data providers on 827 test methods. I don't think you can configure this by the annotations and instead its a configuration passed into the runner. Commented Jul 20, 2015 at 18:52

6 Answers 6

23

You need to use dataproviderthreadcount. The threadpoolsize and invocationcount values are not required. See details here.

Sign up to request clarification or add additional context in comments.

8 Comments

hi niharika , Using dataproviderthreadcount solved my problem . However i am able to set this only as cmd line argument . Is there any way to pass the same at annotation level ?
Nope. No way from the annotation level.
thank you clearing that there is no way to provide this at annotation level. Does this mean that all the tests that use any dataprovider will use the number of tests specified using dataproviderthreadcount ? Would it be possible to control the number of threads based on the test rather than letting all the tests use multiple threads?
AFAIK it is at the run level and cannot be controlled at test level - if I am understanding your question correctly
Okay . That was the exact info i was looking for.
|
4

Try to set the thread pool in following way:

@BeforeClass public void setupClassName(ITestContext context) { context.getCurrentXmlTest().getSuite().setDataProviderThreadCount(5); context.getCurrentXmlTest().getSuite().setPreserveOrder(false); } 

Comments

4

You can achieve this by adding extra configuration 'parallel=true', along with the name of the DataProvider, in its definition. An example is as follows:

@DataProvider(name="InvalidLoginDataProvider", parallel = true) public Object[][] myDataProviderMethod(){ ... ... } 

As per TestNG documentation, the @Test thread pool (created using invocationCount and threadPoolSize parameters in @Test) and Data provider thread pool are different and managed differently.
So, to specify how many threads in Data provider thread pool, one has to add the following configuration in testng.xml file.

<suite name="Suite1" data-provider-thread-count="20" > ... ... </suite> 

HTH!

Comments

3

In testng.xml you can set thread count for the dataprovider via data-provider-thread-count="3"

<suite name="Manage" data-provider-thread-count="3" > <test name="Manage data tests"> <classes> <class name="uk.example.ExampleTest"></class> </classes> </test> </suite> 

Comments

1

Currently only one thread is getting used as you have define invocationCount as 1, if you change it to 3 then three workers thread will get used.

invocationCount :- The number of times this method should be invoked.

threadPoolSize :- The size of the thread pool for this method. The method will be invoked from multiple threads as specified by invocationCount. Note: this attribute is ignored if invocationCount is not specified.

Also,

You can also specify that a @Test method should be invoked from different threads. You can use the attribute threadPoolSize to achieve this result:

@Test(threadPoolSize = 3, invocationCount = 10, timeOut = 10000) public void testServer() { 

In this example, the function testServer will be invoked ten times from three different threads. Additionally, a time-out of ten seconds guarantees that none of the threads will block on this thread forever.

More info can be found here

3 Comments

Hi, I tried that approach but my question is specifically regarding parallel execution with data provider. I am trying to run the test parallelly using dataprovider. Specifying invocation count as 3 in this case would result in the method being invoked 10 times for each input from data provider which account for 8 * 3 = 24 runs.
Data provider will not help in running it parallel.. it's a way to describe your input which call you'er test 1 by 1 using those inputs - IMHO
Hi , dataproviderthreadcount can be used to simulate parallel execution of the single test method with the data instances that come from dataprovider. Data provider thread pool is different from the test thread pool in testng. However dataproviderthreadcount is specified as a cmd line argument . I would like to know if it is possible to specify this at annotation level.
1

I think there is a way to set it on annotation level, it should be add on the DataProvider's :

@DataProvider(name="quick-screen-list", parallel = true) public Object[][] quickScreenDataProvider() { ..... 

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.