Package-level test organization in JUnit

Introduction

Organizing tests by package helps keep related tests together. It makes tests easier to find and maintain.

When you have many tests for different parts of your application.

When you want to run all tests related to a specific feature or module.

When you want to share setup or utility code among tests in the same package.

When you want to keep your project clean and easy to navigate.

When you want to run tests selectively by package in your build tool or IDE.

Syntax

JUnit

src/test/java/com/example/myapp/service/
  MyServiceTest.java
src/test/java/com/example/myapp/repository/
  MyRepositoryTest.java

Tests are placed in the same package structure as the source code but under src/test/java.

This helps tools and IDEs recognize and run tests by package.

Examples

A simple test class placed in the service package.

JUnit

package com.example.myapp.service;

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

public class MyServiceTest {
    @Test
    void testServiceMethod() {
        assertTrue(true);
    }
}

Another test class in the repository package.

JUnit

package com.example.myapp.repository;

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

public class MyRepositoryTest {
    @Test
    void testRepositoryMethod() {
        assertEquals(5, 2 + 3);
    }
}

Sample Program

Two test classes in different packages. Each tests a small part of the application. Running tests by package will run only tests in that package.

JUnit

package com.example.myapp.service;

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

public class CalculatorTest {
    @Test
    void testAddition() {
        int result = 2 + 3;
        assertEquals(5, result);
    }
}

// Separate file: UserRepositoryTest.java
package com.example.myapp.repository;

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

public class UserRepositoryTest {
    @Test
    void testUserCount() {
        int count = 10;
        assertTrue(count > 0);
    }
}

Important Notes

Keep test packages matching source code packages for clarity.

Use your IDE or build tool to run tests by package easily.

Package-level organization helps when your project grows bigger.

Summary

Organize tests in packages matching your source code.

This makes tests easier to find and run selectively.

Helps keep your project clean and maintainable.