Package-level test organization in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why organize tests at the package level?

In JUnit testing, what is the main advantage of organizing tests at the package level?

A It automatically generates test data for all classes in the package.

B It allows running all tests in a package together, improving test management and reporting.

C It prevents tests from accessing classes outside their package, increasing security.

D It forces tests to be run only one by one, reducing parallel execution.

💡 Hint

Think about how grouping tests helps when running many tests.

Organizing tests by package lets you run all tests in that package at once, making it easier to manage and see results collectively.

❓ Predict Output

intermediate

JUnit package-level test suite execution result

Given this JUnit 5 package-level test suite setup, what will be the output when running the suite?

JUnit

package com.example.tests;

import org.junit.platform.suite.api.SelectPackages;
import org.junit.platform.suite.api.Suite;

@Suite
@SelectPackages("com.example.tests.unit")
public class UnitTestsSuite {
}

// Assume com.example.tests.unit contains 3 test classes each with 2 tests, all passing.

A The suite runs only one test from each class, total 3 tests.

B The suite runs no tests because @SelectPackages is ignored at class level.

C The suite runs all 6 tests from the 3 classes and reports all passed.

D The suite runs tests but reports failures due to missing @Test annotations.

💡 Hint

Check how @SelectPackages works with @Suite in JUnit 5.

@SelectPackages tells JUnit to run all tests in the specified package. Since each class has 2 passing tests, total 6 tests run and pass.

❓ locator

advanced

Best locator for package-level test suite class

Which of the following is the best Java package and class name for a package-level test suite that runs all tests in com.app.services?

A com.app.services.ServiceTestSuite

B com.app.AllServicesSuite

C com.app.services.testsuite

D com.app.services.AllServicesTests

💡 Hint

Consider Java naming conventions and clarity for test suite classes.

Option A uses proper camel case and clearly indicates it is a test suite for services in the package.

❓ assertion

advanced

Assertion to verify package-level test suite runs all tests

In a JUnit 5 test suite that runs all tests in com.example.api, which assertion best verifies that exactly 10 tests were executed?

A assertEquals(10, testExecutionSummary.getTestsFailedCount())

B assertTrue(testExecutionSummary.getTestsFoundCount() == 10)

C assertEquals(10, testExecutionSummary.getTestsSucceededCount())

D assertEquals(10, testExecutionSummary.getTestsStartedCount())

💡 Hint

Think about which count reflects total tests run, regardless of pass/fail.

getTestsStartedCount() returns the number of tests that started execution, matching total tests run.

❓ framework

expert

Debugging package-level test suite execution failure

You created a JUnit 5 package-level test suite using @Suite and @SelectPackages("com.app.features"), but no tests run. What is the most likely cause?

A The package name in @SelectPackages is misspelled or does not match actual package.

B The suite class is missing the @RunWith annotation.

C The test classes in com.app.features lack @Test annotations on methods.

D JUnit 5 does not support package-level test suites.

💡 Hint

Check the package name spelling and case carefully.

If the package name in @SelectPackages does not exactly match the package containing tests, no tests will be found or run.