如何关联Cucumber Feature（步骤定义）与TestNG @Test？多浏览器并行运行Cucumber测试

Hey there! Let's break down your two Cucumber + TestNG questions with practical, actionable solutions:

Cucumber and TestNG integrate smoothly using Cucumber's TestNG adapter classes. Here are two reliable approaches:

• Approach 1: Use Cucumber's TestNG Runner Class
  Create a test class that extends AbstractTestNGCucumberTests and add the @CucumberOptions annotation to point to your Feature files and step definitions. Cucumber automatically converts each Scenario into a TestNG @Test method, so you don't need to write explicit @Test annotations yourself. Example code:

  import io.cucumber.testng.AbstractTestNGCucumberTests;
  import io.cucumber.testng.CucumberOptions;
  
  @CucumberOptions(
      features = "src/test/resources/features", // Path to your Feature files
      glue = "com.yourpackage.stepdefinitions", // Package containing step definitions
      plugin = {"pretty", "html:target/cucumber-reports"} // Reporting plugins
  )
  public class CucumberTestNGRunner extends AbstractTestNGCucumberTests {
      // No extra code needed here—AbstractTestNGCucumberTests handles the @Test mapping
  }
  

• Approach 2: Custom TestNG Methods with Cucumber Runtime
  If you want manual control over which Features/Scenarios map to @Test methods, you can invoke Cucumber's Runtime directly within a TestNG @Test method. This is useful for granular test execution control:

  import org.testng.annotations.Test;
  import io.cucumber.runtime.Runtime;
  import io.cucumber.runtime.RuntimeOptions;
  import io.cucumber.runtime.RuntimeOptionsBuilder;
  
  public class CustomCucumberTestNG {
  
      @Test
      public void runLoginFeature() {
          RuntimeOptions options = new RuntimeOptionsBuilder()
              .addGlue("com.yourpackage.stepdefinitions")
              .addFeature("src/test/resources/features/login.feature")
              .build();
          
          Runtime runtime = Runtime.builder()
              .runtimeOptions(options)
              .classLoader(getClass().getClassLoader())
              .build();
          
          runtime.run(); // Executes the specified Feature as a TestNG @Test
      }
  }
  

Your existing browser initialization code is a great start—let's adapt it to work with Cucumber + TestNG parallelism, while ensuring thread safety for WebDriver instances:

Step 1: Configure TestNG XML for Parallel Runs #

Create a testng.xml file to define parallel test suites for each browser. This tells TestNG to spin up separate threads for each browser:

<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd" >
<suite name="Cucumber Parallel Suite" parallel="tests" thread-count="3">
    <!-- IE Test Suite -->
    <test name="IE Test">
        <parameter name="myBrowser" value="ie"/>
        <classes>
            <class name="com.yourpackage.CucumberTestNGRunner"/>
        </classes>
    </test>

    <!-- Chrome Test Suite -->
    <test name="Chrome Test">
        <parameter name="myBrowser" value="chrome"/>
        <classes>
            <class name="com.yourpackage.CucumberTestNGRunner"/>
        </classes>
    </test>

    <!-- Firefox Test Suite -->
    <test name="Firefox Test">
        <parameter name="myBrowser" value="firefox"/>
        <classes>
            <class name="com.yourpackage.CucumberTestNGRunner"/>
        </classes>
    </test>
</suite>

• parallel="tests" means each <test> block runs in its own thread
• thread-count="3" sets the maximum number of concurrent threads

Step 2: Update the Cucumber TestNG Runner with Thread-Safe WebDriver #

Use ThreadLocal to ensure each parallel thread gets its own WebDriver instance (critical for avoiding race conditions). Update your runner class like this:

import io.cucumber.testng.AbstractTestNGCucumberTests;
import io.cucumber.testng.CucumberOptions;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.ie.InternetExplorerDriver;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Parameters;

@CucumberOptions(
    features = "src/test/resources/features",
    glue = "com.yourpackage.stepdefinitions",
    plugin = {"pretty", "html:target/cucumber-reports"}
)
public class CucumberTestNGRunner extends AbstractTestNGCucumberTests {
    // ThreadLocal ensures each thread has its own WebDriver instance
    private static final ThreadLocal<WebDriver> driverThreadLocal = new ThreadLocal<>();

    @Parameters("myBrowser")
    @BeforeClass
    public void launchBrowser(String myBrowser) {
        WebDriver driver = null;
        switch (myBrowser.toLowerCase()) {
            case "ie":
                System.setProperty("webdriver.ie.driver", "C:\\Driver\\IEDriverServer\\IEDriverServer_32bits.exe");
                driver = new InternetExplorerDriver();
                break;
            case "chrome":
                System.setProperty("webdriver.chrome.driver", "path/to/chromedriver.exe");
                driver = new ChromeDriver();
                break;
            case "firefox":
                System.setProperty("webdriver.gecko.driver", "path/to/geckodriver.exe");
                driver = new FirefoxDriver();
                break;
            default:
                throw new IllegalArgumentException("Unsupported browser: " + myBrowser);
        }
        driver.manage().window().maximize();
        driverThreadLocal.set(driver);
    }

    // Helper method to get the WebDriver in step definitions
    public static WebDriver getDriver() {
        return driverThreadLocal.get();
    }

    @AfterClass
    public void tearDownBrowser() {
        WebDriver driver = driverThreadLocal.get();
        if (driver != null) {
            driver.quit();
            driverThreadLocal.remove(); // Clean up the ThreadLocal instance
        }
    }
}

Step 3: Use the Thread-Safe Driver in Step Definitions #

In your step definition classes, fetch the WebDriver using the runner's getDriver() method:

import io.cucumber.java.en.Given;
import static com.yourpackage.CucumberTestNGRunner.getDriver;

public class LoginStepDefinitions {

    @Given("I am on the login page")
    public void i_am_on_the_login_page() {
        getDriver().get("https://your-test-application.com/login");
    }
}

Now, when you run the testng.xml file, TestNG will execute your Cucumber Features in parallel across IE, Chrome, and Firefox. Just make sure your browser driver versions match the installed browser versions to avoid compatibility issues!

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