Maven dependency setup in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

JUnit 5 Maven Dependency Output

What will happen if you run a JUnit 5 test with the following Maven dependency setup in your pom.xml?

JUnit

<dependency>
  <groupId>org.junit.jupiter</groupId>
  <artifactId>junit-jupiter-api</artifactId>
  <version>5.9.2</version>
  <scope>test</scope>
</dependency>

A Build fails because the <scope>test</scope> is invalid for JUnit dependencies.

B Tests run successfully with JUnit 5 features available.

C Tests fail to run because the <artifactId> is incorrect for JUnit 5.

D Tests run but only with JUnit 4 features, not JUnit 5.

💡 Hint

Check if the dependency includes the correct groupId, artifactId, and version for JUnit 5.

The dependency shown is the correct way to include JUnit 5 API for testing in Maven. The test means it is only used during testing and does not affect the main build. This setup allows tests to run with JUnit 5 features.

❓ assertion

intermediate

Correct Assertion for Maven Dependency Presence

Which assertion correctly verifies that the JUnit 5 dependency is included in the Maven project during a build?

A assertFalse(project.getDependencies().contains("junit-jupiter-api"));

B assertEquals("junit-jupiter-api", project.getDependencies().get(0).getGroupId());

C assertTrue(project.getDependencies().stream().anyMatch(d -> d.getArtifactId().equals("junit-jupiter-api")));

D assertNull(project.getDependencies().stream().filter(d -> d.getArtifactId().equals("junit-jupiter-api")).findFirst());

💡 Hint

Look for an assertion that checks if any dependency has the correct artifactId.

Option C correctly checks if any dependency in the project has the artifactId 'junit-jupiter-api'. Other options either check wrong fields or assert the opposite.

🔧 Debug

advanced

Debugging Missing JUnit 5 Dependency Error

You added the JUnit 5 dependency in your pom.xml but Maven reports: Cannot find symbol: @Test when running tests. What is the most likely cause?

A The dependency is declared in the <dependencies> section but not in the <build> plugins.

B The JUnit 5 dependency version is too old and does not support @Test annotation.

C The <artifactId> is set to 'junit-jupiter-engine' instead of 'junit-jupiter-api'.

D The <scope>test</scope> is missing, so the dependency is not included during test compilation.

💡 Hint

Check if the dependency is available during the test phase.

If test is missing, Maven does not include the dependency during test compilation, causing the @Test annotation to be unknown.

🧠 Conceptual

advanced

Understanding Maven Dependency Scopes for Testing

Which Maven dependency scope is best suited for JUnit 5 dependencies and why?

A <scope>test</scope> because it includes the dependency only during testing and not in the final build artifact.

B <scope>compile</scope> because tests need the dependency during compilation and runtime.

C <scope>runtime</scope> because the dependency is only needed when running tests, not compiling.

D <scope>provided</scope> because the dependency is provided by the JDK during tests.

💡 Hint

Think about when test dependencies are needed in the build lifecycle.

The test means the dependency is only used during the test phase and is not included in the final packaged application. This is ideal for testing libraries like JUnit.

❓ framework

expert

Maven Surefire Plugin Configuration for JUnit 5

Which Maven Surefire plugin configuration snippet correctly enables running JUnit 5 tests?

JUnit

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

A

<configuration>
  <providers>
    <provider>
      <name>junit-platform</name>
    </provider>
  </providers>
</configuration>

B

<configuration>
  <useModulePath>false</useModulePath>
</configuration>

C

<configuration>
  <includes>
    <include>**/*Test.java</include>
  </includes>
</configuration>

D

<configuration>
  <testSourceDirectory>src/test/java</testSourceDirectory>
</configuration>

💡 Hint

JUnit 5 requires the Surefire plugin to use the junit-platform provider.

Option A configures the Surefire plugin to use the junit-platform provider, which is necessary to run JUnit 5 tests. Other options do not enable JUnit 5 support explicitly.