TestNG并行执行测试未达预期问题排查求助

Hey there! Let’s break down the most common reasons your parallel test setup isn’t working as expected, and walk through fixes step by step.

1. First: Complete & Validate Your testng.xml Configuration #

Your IE11 test node is incomplete, so let’s start by fixing that. Make sure the IE test block matches the structure of your Chrome one, with unique, correct parameters for the IE node:

<suite name="Parallel" parallel="tests">
    <test name="Performance Test Chrome">
        <parameter name="browser" value="Chrome"/>
        <parameter name="remoteURL" value="http://myIP1:5555/wd/hub"/>
        <parameter name="user" value="user1"/>
        <classes>
            <class name="com.TestClass"/>
        </classes>
    </test>
    <!-- Complete IE11 test configuration -->
    <test name="Performance Test IE11">
        <parameter name="browser" value="IE11"/>
        <!-- Use the correct IP/port for your IE11 node -->
        <parameter name="remoteURL" value="http://myIP2:5556/wd/hub"/>
        <parameter name="user" value="user1"/> <!-- Adjust if needed -->
        <classes>
            <class name="com.TestClass"/>
        </classes>
    </test>
</suite>

• Double-check that parallel="tests" is set on the <suite> tag—this tells TestNG to run each <test> block in its own independent thread, which is exactly what you need for separate browser nodes.
• Ensure the remoteURL for IE11 points to the correct Selenium Grid node (not the same IP/port as Chrome).

2. Verify Your Selenium Grid Node Setup #

Parallel tests fail if your nodes aren’t registered correctly or configured for their browsers:

For the IE11 Node: #

• Confirm you started the node with the right capabilities and driver setup. A valid startup command looks like this:

  java -jar selenium-server-standalone.jar -role node -hub http://your-hub-ip:4444/grid/register -port 5556 -browser browserName="internet explorer",version="11",platform="WINDOWS" -maxSession 1 -Dwebdriver.ie.driver="C:\path\to\IEDriverServer.exe"
  

• Fix critical IE11 prerequisites:
  • Set "Protected Mode" settings to the same state (on or off) for all IE security zones.
  • Ensure IE’s zoom level is set to 100%.
  • The IEDriverServer.exe path must be correctly specified (either via -Dwebdriver.ie.driver or added to your system PATH).

For Both Nodes: #

• Visit your Selenium Grid console (http://your-hub-ip:4444/grid/console) to confirm both Chrome and IE11 nodes are online, and their browser capabilities match what you’ve defined in testng.xml.

3. Ensure Your Test Code Is Thread-Safe #

The #1 cause of parallel test failures is shared state between threads. Make sure your TestClass doesn’t use static WebDriver instances:

public class TestClass {
    // Use an instance variable, not static
    private WebDriver driver;

    @BeforeMethod
    @Parameters({"browser", "remoteURL"})
    public void setUp(String browser, String remoteURL) throws MalformedURLException {
        DesiredCapabilities caps = new DesiredCapabilities();
        if (browser.equalsIgnoreCase("Chrome")) {
            caps.setBrowserName("chrome");
        } else if (browser.equalsIgnoreCase("IE11")) {
            caps.setBrowserName("internet explorer");
            caps.setVersion("11");
        }
        // Initialize a new driver for each test method/thread
        driver = new RemoteWebDriver(new URL(remoteURL), caps);
    }

    @AfterMethod
    public void tearDown() {
        // Always quit the driver to clean up resources
        if (driver != null) {
            driver.quit();
        }
    }

    // Your test methods go here
}

• Avoid static variables for test data or utilities too—each thread should have its own isolated context.

4. Check for Conflicting Parallel Settings #

If you’re using build tools like Maven, make sure they aren’t overriding your testng.xml parallel configuration. For example, in the Maven Surefire plugin, don’t set a parallel parameter unless you want to override the suite file:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>3.0.0-M7</version>
    <configuration>
        <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
        </suiteXmlFiles>
        <!-- Remove any parallel/threadCount settings here to use testng.xml's config -->
    </configuration>
</plugin>

5. Dig Into Logs for Specific Errors #

If the above steps don’t fix things, check the logs:

• TestNG execution logs: Look for thread startup failures or parameter mismatches.
• Selenium Hub/Node logs: Check for errors like "capabilities not matched" or "connection refused" (which means your test can’t reach the node).

Start with these checks, and you’ll likely pinpoint the issue quickly!

内容的提问来源于stack exchange，提问作者Ragnarsson