@AfterAll method in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the @AfterAll method in JUnit?

The <code>@AfterAll</code> method runs once after all test methods in a class have finished. It is used to clean up resources shared by tests, like closing database connections.

intermediate

How must a method annotated with @AfterAll be declared in JUnit 5?

It must be <strong>static</strong> unless the test class is annotated with <code>@TestInstance(TestInstance.Lifecycle.PER_CLASS)</code>. This ensures it runs once after all tests.

beginner

Example of a simple @AfterAll method in JUnit 5:

  @AfterAll
  static void cleanup() {
    System.out.println("All tests done. Cleaning up.");
  }

intermediate

What happens if an exception is thrown inside an @AfterAll method?

The exception is reported as a test failure or error after all tests complete. It can affect the test report but does not stop other tests since it runs last.

beginner

Why use @AfterAll instead of @AfterEach?

@AfterAll runs once after all tests, good for expensive cleanup. @AfterEach runs after every test, which can be slower and redundant for shared resources.

What is the correct signature for an @AfterAll method in JUnit 5 without @TestInstance?

A public static void methodName()

B public void methodName()

C private void methodName()

D protected void methodName()

@AfterAll methods must be static unless the class uses @TestInstance(TestInstance.Lifecycle.PER_CLASS).

When is an @AfterAll method executed?

A Before each test method

B Once after all test methods in the class

C After each test method

D Before all test methods in the class

@AfterAll runs once after all tests finish.

Which annotation allows @AfterAll methods to be non-static?

A @TestInstance(TestInstance.Lifecycle.PER_CLASS)

B @TestInstance(Lifecycle.PER_METHOD)

C @BeforeAll

D @Test

Using @TestInstance(TestInstance.Lifecycle.PER_CLASS) lets @AfterAll methods be instance methods.

What is a common use case for @AfterAll?

A Initialize test data before each test

B Skip a test method

C Run a test multiple times

D Clean up shared resources after all tests

@AfterAll is used to clean up resources shared by all tests.

If an exception occurs in @AfterAll, what happens?

A Tests stop immediately

B Exception is ignored

C Exception is reported after all tests

D Tests rerun automatically

Exceptions in @AfterAll are reported after all tests complete.

Explain the role and requirements of the @AfterAll method in JUnit testing.

Think about when and why you would close shared resources.

Describe the difference between @AfterEach and @AfterAll annotations.

Consider how often each method runs during testing.