Gradle test task in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of Gradle test task with failing test

Given the following JUnit test class, what will be the output status of the Gradle test task when executed?

JUnit

import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.*;

public class SampleTest {
    @Test
    void testSuccess() {
        assertEquals(2, 1 + 1);
    }

    @Test
    void testFailure() {
        assertTrue(false);
    }
}

A The Gradle test task will fail and report 1 failed test.

B The Gradle test task will pass with all tests successful.

C The Gradle test task will fail with a compilation error.

D The Gradle test task will be skipped due to no tests found.

💡 Hint

Remember that a failing assertion causes the test to fail and the Gradle test task to fail.

The test class has one test that always fails (assertTrue(false)). Gradle test task runs all tests and fails if any test fails.

❓ assertion

intermediate

Correct assertion to verify test task execution

Which JUnit assertion correctly verifies that the Gradle test task executed exactly 5 tests successfully?

A assertFalse(result.wasSuccessful());

B assertNull(result.getTestCount());

C assertTrue(result.getFailedTests() == 5);

D assertEquals(5, result.getTestCount());

💡 Hint

You want to check the total number of tests run, not failures or null values.

The method getTestCount() returns the total tests run. To verify 5 tests ran successfully, assertEquals(5, result.getTestCount()) is correct.

🔧 Debug

advanced

Debugging Gradle test task skipping tests

You run gradle test but no tests are executed. Which of the following is the most likely cause?

A The <code>build.gradle</code> file is missing the <code>apply plugin: 'java'</code> line.

B Test classes are not named according to Gradle's default pattern (e.g., *Test.java).

C JUnit dependency is declared with <code>testImplementation</code> instead of <code>implementation</code>.

D The <code>src/main/java</code> directory contains the test classes.

💡 Hint

Gradle looks for test classes matching specific name patterns by default.

Gradle runs tests matching patterns like *Test.java by default. If test classes don't match, no tests run.

❓ framework

advanced

Configuring Gradle test task for JUnit 5

Which Gradle configuration snippet correctly enables JUnit 5 platform for the test task?

A

test {
    useTestNG()
}

B

test {
    useJUnit()
}

C

test {
    useJUnitPlatform()
}

D

test {
    useJUnit4()
}

💡 Hint

JUnit 5 requires a specific platform configuration in Gradle.

JUnit 5 tests require useJUnitPlatform() in the Gradle test task to run properly.

🧠 Conceptual

expert

Impact of test task parallel execution on test results

If you configure the Gradle test task to run tests in parallel, which of the following is a potential risk?

A Tests that share mutable static state may produce flaky or inconsistent results.

B Tests will always run faster without any side effects.

C Gradle will ignore test failures and mark the build as successful.

D JUnit will automatically serialize all tests to avoid conflicts.

💡 Hint

Think about what happens when tests run at the same time and share data.

Parallel test execution can cause issues if tests share mutable static data, leading to flaky tests.