Executing Cucumber Feature Files in Parallel
To execute Cucumber feature files in parallel, you can leverage a plugin called cucumber-jvm-parallel-plugin. Here's how to use it:
Add the Plugin to Your POM:
<code class="xml"><dependency> <groupId>com.github.temyers</groupId> <artifactId>cucumber-jvm-parallel-plugin</artifactId> <version>2.1.0</version> </dependency></code>
Configure the Plugin in Your Build:
<code class="xml"><plugin> <groupId>com.github.temyers</groupId> <artifactId>cucumber-jvm-parallel-plugin</artifactId> <version>2.1.0</version> <executions> <execution> <id>generateRunners</id> <phase>generate-test-sources</phase> <goals> <goal>generateRunners</goal> </goals> <configuration> <!-- Package names for glue code --> <glue>com.example.cucumber</glue> <!-- Output directory for generated runner classes --> <outputDirectory>${project.build.directory}/generated-test-sources/cucumber</outputDirectory> <!-- Features directory --> <featuresDirectory>src/test/resources/features/</featuresDirectory> <!-- Output directory for Cucumber reports --> <cucumberOutputDir>target/cucumber-parallel</cucumberOutputDir> <!-- Output format --> <format>json</format> <!-- Strict property --> <strict>true</strict> <!-- Monochrome property --> <monochrome>true</monochrome> <!-- Tags to run --> <tags></tags> <!-- Filter features by tags --> <filterFeaturesByTags>false</filterFeaturesByTags> <!-- Use TestNG runners --> <useTestNG>false</useTestNG> <!-- Naming scheme --> <namingScheme>simple</namingScheme> <!-- Naming pattern --> <namingPattern>Parallel{c}IT</namingPattern> <!-- Parallel scheme --> <parallelScheme>SCENARIO</parallelScheme> </configuration> </execution> </executions> </plugin></code>
Configure Surefire Plugin to Invoke TestNG Runners:
<code class="xml"><plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.19</version> <configuration> <forkCount>5</forkCount> <reuseForks>true</reuseForks> <includes> <include>**/*IT.class</include> </includes> </configuration> </plugin></code>
Share the WebDriver Instance:
In order to avoid having different thread instances of the WebDriver, you must implement a shared WebDriver class that prevents the driver.quit() method from being called:
<code class="java">import org.openqa.selenium.WebDriver; import org.openqa.selenium.firefox.FirefoxDriver; import org.openqa.selenium.support.events.EventFiringWebDriver; public class SharedDriver extends EventFiringWebDriver { private static WebDriver REAL_DRIVER = null; public SharedDriver() { super(CreateDriver()); } public static WebDriver CreateDriver() { WebDriver webDriver; if (REAL_DRIVER == null) { webDriver = new FirefoxDriver(); setWebDriver(webDriver); } return webDriver; } public static void setWebDriver(WebDriver webDriver) { REAL_DRIVER = webDriver; } public static WebDriver getWebDriver() { return REAL_DRIVER; } @Override public void close() { if (Thread.currentThread() != CLOSE_THREAD) { throw new UnsupportedOperationException("You shouldn't close this WebDriver. It's shared and will close when the JVM exits."); } super.close(); } }</code>
Configure Hub to Support Parallel Execution:
If you plan on running more than 50 threads, you need to increase the -DPOOL_MAX value for the Hub.
java -jar selenium-server-standalone-<version>.jar -role hub -DPOOL_MAX=512
Execute the Feature Files:
Run your Cucumber tests in parallel using the command:
mvn test
The above is the detailed content of Here are a few title options based on the provided text, focusing on the \'question\' aspect: Option 1 (More Direct): * How do I run Cucumber feature files in parallel using the `cucumber-. For more information, please follow other related articles on the PHP Chinese website!