Gradle dependency setup in JUnit - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add JUnit Jupiter API as a test dependency in Gradle.

JUnit

dependencies {
    testImplementation '[1]'
}

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

A"org.junit.jupiter:junit-jupiter-api:5.9.3"

B"junit:junit:4.13.2"

C"org.mockito:mockito-core:4.8.0"

D"org.testng:testng:7.7.0"

Attempts:

3 left

💡 Hint

Common Mistakes

Using JUnit 4 dependency instead of JUnit Jupiter.

Forgetting to put the dependency string in quotes.

The correct Gradle dependency for JUnit Jupiter API is org.junit.jupiter:junit-jupiter-api:5.9.3. This adds the JUnit 5 API for writing tests.

2fill in blank

medium

Complete the code to apply the Java plugin in Gradle for testing support.

JUnit

plugins {
    id '[1]'
}

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

A"application"

B"maven"

C"junit"

D"java"

Attempts:

3 left

💡 Hint

Common Mistakes

Using junit as a plugin id, which does not exist.

Using unrelated plugins like application or maven.

The java plugin is required in Gradle to compile Java code and run tests.

3fill in blank

hard

Fix the error in the test task configuration to use JUnit Platform.

JUnit

test {
    use[1]()
}

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

AJUnit4

BJUnitPlatform

CTestNG

DJUnit5

Attempts:

3 left

💡 Hint

Common Mistakes

Using useJUnit5() which does not exist.

Using useJUnit4() which runs only JUnit 4 tests.

To run JUnit 5 tests in Gradle, you must configure the test task to use useJUnitPlatform().

4fill in blank

hard

Fill both blanks to add JUnit Jupiter Engine and enable test logging.

JUnit

dependencies {
    testRuntimeOnly '[1]'
}
test {
    testLogging {
        events [2]
    }
}

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

A"org.junit.jupiter:junit-jupiter-engine:5.9.3"

B["passed", "skipped", "failed"]

C"passed", "skipped", "failed"

D"org.junit.jupiter:junit-jupiter-api:5.9.3"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the API dependency instead of the engine for runtime.

Passing events as a list instead of separate strings.

The JUnit Jupiter Engine is added as a testRuntimeOnly dependency to run tests. The testLogging.events expects a list of event names as strings, so the correct syntax is "passed", "skipped", "failed".

5fill in blank

hard

Fill all three blanks to configure Gradle to use JUnit 5 with correct dependencies and test task.

JUnit

plugins {
    id '[1]'
}
dependencies {
    testImplementation '[2]'
    testRuntimeOnly '[3]'
}
test {
    useJUnitPlatform()
}

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

A"java"

B"org.junit.jupiter:junit-jupiter-api:5.9.3"

C"org.junit.jupiter:junit-jupiter-engine:5.9.3"

D"application"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong plugin id like application.

Mixing up API and engine dependencies.

Forgetting to configure useJUnitPlatform().

The java plugin enables Java compilation and testing. The testImplementation dependency adds the JUnit Jupiter API for writing tests. The testRuntimeOnly dependency adds the JUnit Jupiter Engine to run the tests. The test task uses useJUnitPlatform() to run JUnit 5 tests.

Practice

1. What is the correct Gradle configuration to add JUnit 5 as a test-only dependency?

easy

A. compile 'org.junit.jupiter:junit-jupiter:5.9.3'

B. implementation 'org.junit.jupiter:junit-jupiter:5.9.3'

C. runtimeOnly 'org.junit.jupiter:junit-jupiter:5.9.3'

D. testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3'

Solution

1. Step 1: Understand Gradle dependency scopes

   For testing libraries like JUnit, Gradle uses testImplementation to include dependencies only in the test source set.

2. Step 2: Identify the correct dependency declaration

   The correct syntax is testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3' to add JUnit 5 for tests only.

3. Final Answer:

   testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3' -> Option D

4. Quick Check:

   JUnit test dependency = testImplementation [OK]

Hint: Use testImplementation for test-only libraries like JUnit [OK]

Common Mistakes:

• Using implementation instead of testImplementation
• Using compile which is deprecated
• Using runtimeOnly which excludes compile-time access

2. Which of the following is the correct syntax to add JUnit 5 dependency in Gradle's build.gradle file using the Kotlin DSL?

easy

A. testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3'

B. implementation("org.junit.jupiter:junit-jupiter:5.9.3")

C. testImplementation("org.junit.jupiter:junit-jupiter:5.9.3")

D. compile 'org.junit.jupiter:junit-jupiter:5.9.3'

Solution

1. Step 1: Recognize Kotlin DSL syntax

   Gradle Kotlin DSL uses parentheses and double quotes for dependencies, e.g., testImplementation("group:name:version").

2. Step 2: Identify the correct test dependency syntax

   testImplementation("org.junit.jupiter:junit-jupiter:5.9.3") uses the correct Kotlin DSL syntax for test dependencies.

3. Final Answer:

   testImplementation("org.junit.jupiter:junit-jupiter:5.9.3") -> Option C

4. Quick Check:

   Kotlin DSL uses parentheses and quotes [OK]

Hint: Kotlin DSL uses parentheses and quotes for dependencies [OK]

Common Mistakes:

• Using single quotes in Kotlin DSL
• Using compile which is deprecated
• Mixing Groovy and Kotlin syntax

3. Given this Gradle snippet in Groovy DSL:

dependencies {
    testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3'
    implementation 'com.google.guava:guava:31.1-jre'
}

Which statement is true when running tests?

medium

A. Guava is available only during test runtime.

B. JUnit 5 is available only during test compilation and runtime.

C. JUnit 5 is available during main source compilation.

D. Guava is available only during test compilation.

Solution

1. Step 1: Understand dependency scopes

   testImplementation means the dependency is available only for compiling and running tests, not main code. implementation is for main code and runtime.

2. Step 2: Apply to given dependencies

   JUnit 5 is declared with testImplementation, so it is only for test compilation and runtime. Guava is declared with implementation, so it is available in main code and runtime, not limited to tests.

3. Final Answer:

   JUnit 5 is available only during test compilation and runtime. -> Option B

4. Quick Check:

   testImplementation = test-only scope [OK]

Hint: testImplementation means test-only availability [OK]

Common Mistakes:

• Confusing implementation with testImplementation
• Assuming testImplementation affects main code
• Mixing runtimeOnly with implementation

4. You added this line to your Gradle build file:

testImplementation 'org.junit.jupiter:junit-jupiter:5.9.3'

But your tests fail to run with a "ClassNotFoundException" for JUnit classes. What is the most likely cause?

medium

A. You forgot to apply the 'java' or 'java-library' plugin in build.gradle.

B. You used 'testImplementation' instead of 'implementation'.

C. The JUnit version 5.9.3 does not exist.

D. You need to add 'runtimeOnly' for JUnit.

Solution

1. Step 1: Check plugin application

   Gradle needs the 'java' or 'java-library' plugin to recognize source sets and dependencies properly.

2. Step 2: Understand impact on dependencies

   Without the plugin, Gradle won't configure test source sets, causing ClassNotFoundException even if dependencies are declared.

3. Final Answer:

   You forgot to apply the 'java' or 'java-library' plugin in build.gradle. -> Option A

4. Quick Check:

   Java plugin required for test dependencies [OK]

Hint: Always apply 'java' plugin to enable test dependencies [OK]

Common Mistakes:

• Using implementation instead of testImplementation
• Assuming dependency version is wrong without checking
• Adding runtimeOnly unnecessarily

5. You want to add JUnit 5 and Mockito for testing in your Gradle project. Which is the best way to declare these dependencies to keep your build file organized and efficient?

hard

A. Use testImplementation for both JUnit and Mockito dependencies.

B. Use implementation for JUnit and testImplementation for Mockito.

C. Use runtimeOnly for both JUnit and Mockito.

D. Use compileOnly for JUnit and implementation for Mockito.

Solution

1. Step 1: Understand dependency scopes for testing libraries

   Both JUnit and Mockito are used only during testing, so they should be added with testImplementation to avoid including them in production code.

2. Step 2: Choose consistent and clear dependency declarations

   Using testImplementation for both keeps the build file organized and ensures dependencies are available only for tests.

3. Final Answer:

   Use testImplementation for both JUnit and Mockito dependencies. -> Option A

4. Quick Check:

   Test libraries = testImplementation [OK]

Hint: Put all test libs under testImplementation for clarity [OK]

Common Mistakes:

• Mixing implementation and testImplementation for test libs
• Using runtimeOnly which excludes compile-time access
• Using compileOnly which excludes runtime