Maven Surefire plugin in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Maven Surefire plugin version in the POM file.

JUnit

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>[1]</version>
</plugin>

Drag options to blanks, or click blank then click option'

A2.5

B1.0.0

C3.0.0-M7

D4.0.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using outdated plugin versions like 1.0.0 or 2.5 which may not support JUnit 5.

The version 3.0.0-M7 supports modern JUnit versions.

2fill in blank

medium

Complete the code to configure Maven Surefire plugin to include only tests matching the pattern.

JUnit

<configuration>
  <includes>
    <include>[1]</include>
  </includes>
</configuration>

Drag options to blanks, or click blank then click option'

A**/*Test.java

B*.txt

Csrc/test/java

Dpom.xml

Attempts:

3 left

💡 Hint

Common Mistakes

Using file extensions or paths that do not match Java test files.

The pattern '**/*Test.java' tells Surefire to run all test classes ending with 'Test.java'.

3fill in blank

hard

Fix the error in the Maven Surefire plugin configuration to enable JUnit 5 platform.

JUnit

<configuration>
  <[1]>
    <provider>org.junit.platform.surefire.provider.JUnitPlatformProvider</provider>
  </[1]>
</configuration>

Drag options to blanks, or click blank then click option'

AuseProvider

Bprovider

CproviderName

Dproviders

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular tag directly without wrapping in .

The correct tag is which wraps one or more elements. Using enables specifying the JUnit Platform provider.

4fill in blank

hard

Fill both blanks to configure Maven Surefire plugin to run tests with JUnit 5 and enable detailed reports.

JUnit

<configuration>
  <[1]>
    <[2]>org.junit.platform.surefire.provider.JUnitPlatformProvider</[2]>
  </[1]>
  <reportsDirectory>${project.build.directory}/surefire-reports</reportsDirectory>
</configuration>

Drag options to blanks, or click blank then click option'

Aproviders

Bprovider

CuseJUnitPlatform

DreportFormat

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect tag names like or which are not valid here.

The tag wraps one or more tags. The provider specifies the JUnit Platform provider class to run JUnit 5 tests.

5fill in blank

hard

Fill all three blanks to configure Maven Surefire plugin to skip tests and set a custom test failure ignore flag.

JUnit

<configuration>
  <[1]>true</[1]>
  <[2]>false</[2]>
  <[3]>true</[3]>
</configuration>

Drag options to blanks, or click blank then click option'

AskipTests

BtestFailureIgnore

CforkCount

DfailIfNoTests

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing forkCount (which is a number) with boolean flags.

Setting testFailureIgnore to true when you want build to fail on test errors.

true skips running tests.
false means build fails on test failures.
true fails build if no tests are found.

Practice

1. What is the main purpose of the Maven Surefire plugin in a JUnit testing project?

easy

A. To deploy the application to a server

B. To compile Java source code

C. To run tests automatically during the build process

D. To package the application into a JAR file

Solution

1. Step 1: Understand the role of Maven Surefire plugin

   The Maven Surefire plugin is designed to run tests automatically during the build process, ensuring code correctness early.

2. Step 2: Differentiate from other Maven plugins

   Other plugins like compiler or deploy handle compiling or deployment, not running tests.

3. Final Answer:

   To run tests automatically during the build process -> Option C

4. Quick Check:

   Maven Surefire runs tests during build [OK]

Hint: Surefire runs tests during build, not compile or deploy [OK]

Common Mistakes:

• Confusing Surefire with compiler plugin
• Thinking Surefire packages the app
• Assuming Surefire deploys the app

2. Which XML tag correctly configures the Maven Surefire plugin in the pom.xml file?

easy

A. org.apache.maven.pluginsmaven-jar-plugin

B. org.apache.maven.pluginsmaven-compiler-plugin

C. org.junit.jupiterjunit-jupiter-engine

D. org.apache.maven.pluginsmaven-surefire-plugin

Solution

1. Step 1: Identify the correct plugin artifactId for Surefire

   The Maven Surefire plugin uses maven-surefire-plugin as its artifactId.

2. Step 2: Confirm groupId and artifactId match Surefire plugin

   The groupId is org.apache.maven.plugins, which is standard for Maven plugins.

3. Final Answer:

   <plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId></plugin> -> Option D

4. Quick Check:

   Surefire plugin artifactId = maven-surefire-plugin [OK]

Hint: Surefire plugin artifactId always contains 'surefire' [OK]

Common Mistakes:

• Using maven-compiler-plugin instead of surefire
• Confusing JUnit engine with Surefire plugin
• Using maven-jar-plugin for testing

3. Given this pom.xml snippet, what will happen when you run mvn test?

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>3.0.0-M7</version>
  <configuration>
    <includes>
      <include>**/*Test.java</include>
    </includes>
  </configuration>
</plugin>

medium

A. Only Java files ending with 'Test.java' will be run as tests

B. All Java files will be compiled but no tests will run

C. Tests will run only if file names start with 'Test'

D. No tests will run because version is invalid

Solution

1. Step 1: Understand the includes configuration

   The <includes> tag specifies which test files to run. Here, it includes files matching **/*Test.java.

2. Step 2: Interpret the pattern meaning

   The pattern means any Java file ending with 'Test.java' in any folder will be run as a test.

3. Final Answer:

   Only Java files ending with 'Test.java' will be run as tests -> Option A

4. Quick Check:

   Includes pattern '**/*Test.java' runs matching test files [OK]

Hint: Includes '**/*Test.java' runs files ending with 'Test.java' [OK]

Common Mistakes:

• Assuming all Java files run as tests
• Thinking files starting with 'Test' run
• Believing version 3.0.0-M7 is invalid

4. You added the Maven Surefire plugin to your pom.xml but tests are not running. Which of these is the most likely cause?

medium

A. The pom.xml file is not saved

B. The artifactId is misspelled as maven-surefire-plugn

C. The version tag is missing

D. JUnit tests are written in a different folder than src/test/java

Solution

1. Step 1: Check plugin artifactId spelling

   If the artifactId is misspelled, Maven cannot find the plugin, so tests won't run.

2. Step 2: Consider other causes

   Missing version usually defaults to latest, unsaved pom.xml is unlikely, and test folder location matters but less common cause.

3. Final Answer:

   The artifactId is misspelled as maven-surefire-plugn -> Option B

4. Quick Check:

   Misspelled artifactId stops Surefire plugin loading [OK]

Hint: Check artifactId spelling first if tests don't run [OK]

Common Mistakes:

• Ignoring typo in artifactId
• Assuming missing version always breaks build
• Not verifying test source folder

5. You want to run only tests tagged with @Fast annotation using Maven Surefire plugin. Which configuration snippet in pom.xml achieves this?

hard

A. Fast

B. Fast

C. **/*Fast.java

D. Fast*

Solution

1. Step 1: Understand Surefire's group filtering

   Surefire uses <groups> to include tests with specific JUnit categories or tags.

2. Step 2: Match the correct tag for including groups

   Using <groups>Fast</groups> runs only tests tagged with @Fast.

3. Final Answer:

   <configuration><groups>Fast</groups></configuration> -> Option A

4. Quick Check:

   Use <groups> to run tagged tests [OK]

Hint: Use <groups> tag to run tests with specific annotations [OK]

Common Mistakes:

• Using excludedGroups instead of groups
• Filtering by filename instead of annotation
• Using <test> tag incorrectly