Gradle dependency setup in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Gradle test task configuration?

Given the following Gradle build snippet, what will be the result when running ./gradlew test?

JUnit

plugins {
    id 'java'
}

dependencies {
    testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'
    testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
}

test {
    useJUnitPlatform()
    testLogging {
        events 'passed', 'failed'
    }
}

A Build fails due to missing JUnit engine dependency

B Tests run using JUnit 4 platform, but no test events are shown in the console

C Tests run using JUnit 5 platform, showing passed and failed test events in the console

D Tests run but no test results are displayed because testLogging is not configured

💡 Hint

Check which JUnit version is configured and how testLogging is set.

The configuration uses JUnit Jupiter API and engine dependencies for JUnit 5. The useJUnitPlatform() enables JUnit 5 test discovery. The testLogging block configures the console to show passed and failed test events.

❓ assertion

intermediate

Which Gradle dependency scope is correct for JUnit 5 API?

You want to write tests using JUnit 5 API in Gradle. Which dependency configuration should you use?

A testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'

B implementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'

C runtimeOnly 'org.junit.jupiter:junit-jupiter-api:5.9.2'

D compileOnly 'org.junit.jupiter:junit-jupiter-api:5.9.2'

💡 Hint

JUnit API is only needed when compiling test code, not main code.

The testImplementation scope is used for dependencies required to compile and run test source code. JUnit API is needed only for test compilation and execution, so testImplementation is correct.

🔧 Debug

advanced

Why does the Gradle test task not run any tests?

Given this Gradle snippet, tests are not detected or run. What is the cause?

JUnit

plugins {
    id 'java'
}

dependencies {
    testImplementation 'junit:junit:4.13.2'
}

test {
    useJUnitPlatform()
}

A JUnit dependency version is outdated and causes build failure

B JUnit 4 dependency is used but <code>useJUnitPlatform()</code> requires JUnit 5 tests

C Missing <code>testRuntimeOnly</code> dependency for JUnit engine

D The <code>test</code> task is missing <code>testLogging</code> configuration

💡 Hint

Check compatibility between JUnit version and test platform used.

The useJUnitPlatform() enables JUnit 5 test discovery. Using JUnit 4 dependency alone means no JUnit 5 tests are found, so no tests run.

❓ framework

advanced

How to configure Gradle to run JUnit 5 tests with parameterized support?

You want to run JUnit 5 tests including parameterized tests. Which dependencies and configuration are correct?

A

testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'
testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
testImplementation 'org.junit.jupiter:junit-jupiter-params:5.9.2'
test { useJUnitPlatform() }

B

testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'
testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
test { useJUnitPlatform() }

C

implementation 'org.junit.jupiter:junit-jupiter-api:5.9.2'
runtimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.9.2'
test { useJUnitPlatform() }

D

testImplementation 'junit:junit:4.13.2'
test { useJUnitPlatform() }

💡 Hint

Parameterized tests need a separate JUnit 5 params dependency.

JUnit 5 parameterized tests require the junit-jupiter-params dependency. The API and engine dependencies are also needed. The useJUnitPlatform() enables JUnit 5 test discovery.

🧠 Conceptual

expert

What is the effect of missing testRuntimeOnly dependency for JUnit engine in Gradle?

If you declare only testImplementation 'org.junit.jupiter:junit-jupiter-api:5.9.2' but omit testRuntimeOnly 'org.junit.jupiter:junit-jupiter-engine:5.9.2', what happens when running tests?

A Build fails during compilation due to missing engine classes

B Tests run but no test results are reported

C Tests run successfully because API includes engine classes

D Tests compile but fail at runtime with ClassNotFoundException for JUnit engine classes

💡 Hint

Consider the role of API vs engine dependencies in JUnit 5.

The API dependency provides test annotations and interfaces for compilation. The engine dependency is required at runtime to execute tests. Omitting the engine causes runtime failures.