Why assertNull and assertNotNull in JUnit? - Purpose & Use Cases

The Big Idea

What if you could instantly know if something important is missing or present without digging through details?

The Scenario

Imagine you are checking if a box is empty or not by opening it and looking inside every single time.

Now, think about doing this for hundreds of boxes manually, one by one, to make sure they are empty or filled as expected.

The Problem

Manually opening each box is slow and tiring.

You might miss some boxes or make mistakes about whether they are empty or not.

This leads to errors and wastes a lot of time.

The Solution

Using assertNull and assertNotNull in tests is like having a smart helper who quickly checks if a box is empty or not without opening it.

This helper tells you immediately if something is wrong, saving time and avoiding mistakes.

Before vs After

✗ Before

if (object == null) {
  System.out.println("Object is null");
} else {
  System.out.println("Object is not null");
}

✓ After

assertNull(object); // when expecting null
assertNotNull(object); // when expecting not null

What It Enables

It enables fast, clear, and reliable checks that objects are empty or present exactly when they should be.

Real Life Example

When testing a login system, assertNull can check that a user session is empty before login, and assertNotNull confirms the session is created after login.

Key Takeaways

Manual checks for null values are slow and error-prone.

assertNull and assertNotNull provide quick, automatic verification.

They help catch problems early and keep tests simple and clear.