org.junit.jupiter.api.AfterAll Maven / Gradle / Ivy
Show all versions of junit-jupiter-api Show documentation
/*
* Copyright 2015-2024 the original author or authors.
*
* All rights reserved. This program and the accompanying materials are
* made available under the terms of the Eclipse Public License v2.0 which
* accompanies this distribution and is available at
*
* https://www.eclipse.org/legal/epl-v20.html
*/
package org.junit.jupiter.api;
import static org.apiguardian.api.API.Status.STABLE;
import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import org.apiguardian.api.API;
/**
* {@code @AfterAll} is used to signal that the annotated method should be
* executed after all tests in the current test class.
*
* In contrast to {@link AfterEach @AfterEach} methods, {@code @AfterAll}
* methods are only executed once for a given test class.
*
*
Method Signatures
*
* {@code @AfterAll} methods must have a {@code void} return type and must
* be {@code static} by default. Consequently, {@code @AfterAll} methods are
* not supported in {@link Nested @Nested} test classes or as interface
* default methods unless the test class is annotated with
* {@link TestInstance @TestInstance(Lifecycle.PER_CLASS)}. However, beginning
* with Java 16 {@code @AfterAll} methods may be declared as {@code static} in
* {@link Nested @Nested} test classes, in which case the {@code Lifecycle.PER_CLASS}
* restriction no longer applies. In addition, {@code @AfterAll} methods may
* optionally declare parameters to be resolved by
* {@link org.junit.jupiter.api.extension.ParameterResolver ParameterResolvers}.
*
*
Using {@code private} visibility for {@code @AfterAll} methods is strongly
* discouraged and will be disallowed in a future release.
*
*
Inheritance and Execution Order
*
* {@code @AfterAll} methods are inherited from superclasses as long as they
* are not overridden according to the visibility rules of the Java
* language. Furthermore, {@code @AfterAll} methods from superclasses will be
* executed after {@code @AfterAll} methods in subclasses.
*
*
Similarly, {@code @AfterAll} methods declared in an interface are inherited
* as long as they are not overridden, and {@code @AfterAll} methods from an
* interface will be executed after {@code @AfterAll} methods in the class that
* implements the interface.
*
*
JUnit Jupiter does not guarantee the execution order of multiple
* {@code @AfterAll} methods that are declared within a single test class or
* test interface. While it may at times appear that these methods are invoked
* in alphabetical order, they are in fact sorted using an algorithm that is
* deterministic but intentionally non-obvious.
*
*
In addition, {@code @AfterAll} methods are in no way linked to
* {@code @BeforeAll} methods. Consequently, there are no guarantees with regard
* to their wrapping behavior. For example, given two
* {@code @BeforeAll} methods {@code createA()} and {@code createB()} as well as
* two {@code @AfterAll} methods {@code destroyA()} and {@code destroyB()}, the
* order in which the {@code @BeforeAll} methods are executed (e.g.
* {@code createA()} before {@code createB()}) does not imply any order for the
* seemingly corresponding {@code @AfterAll} methods. In other words,
* {@code destroyA()} might be called before or after
* {@code destroyB()}. The JUnit Team therefore recommends that developers
* declare at most one {@code @BeforeAll} method and at most one
* {@code @AfterAll} method per test class or test interface unless there are no
* dependencies between the {@code @BeforeAll} methods or between the
* {@code @AfterAll} methods.
*
*
Composition
*
* {@code @AfterAll} may be used as a meta-annotation in order to create
* a custom composed annotation that inherits the semantics of
* {@code @AfterAll}.
*
* @since 5.0
* @see BeforeAll
* @see BeforeEach
* @see AfterEach
* @see Test
* @see TestFactory
* @see TestInstance
*/
@Target({ ElementType.ANNOTATION_TYPE, ElementType.METHOD })
@Retention(RetentionPolicy.RUNTIME)
@Documented
@API(status = STABLE, since = "5.0")
public @interface AfterAll {
}