Maven Surefire plugin in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Surefire Plugin Default Test Inclusion

Given the following Maven Surefire plugin configuration snippet, which test classes will be executed by default?

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>3.0.0-M7</version>
</plugin>

A All classes in the src/main/java directory

B Only classes named exactly Test.java

C Only classes annotated with @RunWith

D All classes matching **/Test*.java, **/*Test.java, and **/*Tests.java

💡 Hint

Think about the default naming patterns Surefire uses to find test classes.

By default, the Surefire plugin runs tests in classes matching patterns like **/Test*.java, **/*Test.java, and **/*Tests.java. It does not restrict to exact names or annotations unless configured.

❓ assertion

intermediate

Surefire Plugin Failsafe vs Surefire

Which assertion about the Maven Surefire and Failsafe plugins is correct?

A Surefire runs unit tests during the test phase; Failsafe runs integration tests during the integration-test phase

B Failsafe runs unit tests during the test phase; Surefire runs integration tests during the integration-test phase

C Both Surefire and Failsafe run tests only during the package phase

D Surefire runs tests only if the project uses JUnit 5

💡 Hint

Consider the Maven lifecycle phases and typical plugin usage.

Surefire is designed to run unit tests during the test phase, while Failsafe is intended for integration tests during the integration-test phase.

🔧 Debug

advanced

Debugging Surefire Test Skipping

A developer notices that no tests run when executing mvn test even though test classes exist. The Surefire plugin is configured as below:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>3.0.0-M7</version>
  <configuration>
    <skipTests>true</skipTests>
  </configuration>
</plugin>

What is the reason tests are not running?

A The <code>skipTests</code> parameter is set to true, so Surefire skips all tests

B Tests are skipped because the <code>test</code> phase is not bound to Surefire by default

C The plugin version 3.0.0-M7 does not support running tests

D Tests are skipped because the test classes are not in the default directory

💡 Hint

Check the plugin configuration parameters related to skipping tests.

The skipTests configuration set to true tells Surefire to skip running tests during the build.

❓ framework

advanced

Surefire Plugin and JUnit 5 Support

Which configuration is required to enable JUnit 5 tests to run with Maven Surefire plugin version 3.0.0-M7?

A No additional configuration is needed; Surefire 3.0.0-M7 supports JUnit 5 by default

B Add <code>&lt;dependency&gt;org.junit.jupiter:junit-jupiter-engine&lt;/dependency&gt;</code> and configure Surefire to use <code>junitPlatform</code> provider

C Use the Failsafe plugin instead of Surefire for JUnit 5 tests

D Add <code>&lt;dependency&gt;junit:junit&lt;/dependency&gt;</code> to support JUnit 5

💡 Hint

Think about the provider and dependencies needed for JUnit 5.

JUnit 5 requires the junit-jupiter-engine dependency and Surefire configured with the junitPlatform provider to run tests.

🧠 Conceptual

expert

Surefire Plugin Parallel Test Execution

Which statement about configuring parallel test execution in Maven Surefire plugin is correct?

A Setting <code>parallel</code> to <code>classes</code> runs test classes sequentially

B Parallel execution is not supported by Surefire plugin

C Setting <code>parallel</code> to <code>methods</code> runs test methods in parallel within the same class

D Surefire requires external tools to run tests in parallel

💡 Hint

Consider the parallel modes Surefire supports.

Surefire supports parallel execution modes such as methods (parallel test methods in a class) and classes (parallel test classes). Setting parallel to methods runs methods in parallel.