TestNG类可以并行运行，但方法不能并行运行。 如何配置testng.xml文件和测试类，以便方法也可以并行运行？

Question

I have a suite of Selenium WebDriver tests that I'm running with Grid. When I run this testng.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite" parallel="classes" thread-count="20">
  <test name="Test">
    <classes>
      <class name="testcases.test1"/>
      <class name="testcases.test2"/>
      <class name="testcases.test3"/>
      <class name="testcases.test4"/>
      <class name="testcases.test5"/>
      <class name="testcases.test6"/>
      <class name="testcases.test7"/>
      <class name="testcases.test8"/>
      <class name="testcases.test9"/>
      <class name="testcases.test10"/>
      <class name="testcases.test11"/>
      <class name="testcases.test12"/>
      <class name="testcases.test13"/>
      <class name="testcases.test14"/>
      <class name="testcases.test15"/>
      <class name="testcases.test16"/>
      <class name="testcases.test17"/>
      <class name="testcases.test18"/>
      <class name="testcases.test19"/>
      <class name="testcases.test20"/>
      <class name="testcases.test21"/>
    </classes>
  </test> <!-- Test -->
</suite> <!-- Suite -->

Multiple browsers open, each running the @BeforeClass method and the first @Test method. However, after each browser finishes that first @Test method, it will wait for all the other browsers to finish their respective first @Test method.

The tests are structured like this:

public class sampleTestClass {
    @BeforeClass
    public void setup(){
        //setup Remote WebDriver
    }
    @Test
    public void method1(){
        //do things
    }
    @Test(dependsOnMethods = "method1")
    public void method2(){
        //do things
    }
    @Test(dependsOnMethods = "method2")
    public void method3(){
        //do things
    }
    @AfterClass
    public void teardown(){
        //call teardown
    }

}

with multiple @Test methods in each class. I will add that everything runs the way I prefer when I use this .xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="MySuite" parallel="tests" thread-count="20">
  <test name="First Test">
    <classes>
       <class name="testcases.test1"/>
    </classes>
  </test>
  <test name="Second Test">
    <classes>
       <class name="testcases.test2"/>
    </classes>
  </test>
  <test name="Third Test">
    <classes>
       <class name="testcases.test3"/>
    </classes>
  </test>
  <test name="Fourth Test">
    <classes>
       <class name="testcases.test4"/>
    </classes>
  </test>
  <!--<test name="Fifth Test">
    <classes>
       <class name="testcases.test5"/>
    </classes>
  </test>-->
  <test name="Sixth Test">
    <classes>
       <class name="testcases.test6"/>
    </classes>
  </test>
  <test name="Seventh Test">
    <classes>
       <class name="testcases.test7"/>
    </classes>
  </test>
</suite>

The reason I'm not okay with this configuration is that one, I don't think it preserves the semantic meaning of the tags at all, and two (and most importantly) I'd like to be able to run the automatically generated suite of failures in parallel, but the configuration of that .xml file is the same as the top one that I'm having trouble with.

It seems to me that specifying parallel="classes" in the suite tag is consistent with the TestNG documentation, but doesn't achieve asynchronous execution of the @Test methods in the separate classes.

Why doesn't this configuration of the .xml file work? What do I need to do differently to make it work?

Answer 1

In the context of a webdriver test class having multiple methods, given that there is one instance of a webdriver in that class, i dont see how it would be possible to share one webdriver instance simultanously between methods. I seems it would HAVE TO call methods one at a time so that each method had its turn with the webdriver instance. Otherwise it seems you would get some sort of concurrent exception.

I've tried many times to get parallel methods working with TestNG but never succeeded. There is an example in the source code though that might be a clue; just look at the testng.xml in the same folder.