Annotation Interface TempDir

@TempDir can be used to annotate a field in a test class or a parameter in a lifecycle method or test method of type Path or File that should be resolved into a temporary directory.

Please note that @TempDir is not supported on constructor parameters. Please use field injection instead by annotating an instance field with @TempDir.


The temporary directory is only created if a field in a test class or a parameter in a lifecycle method or test method is annotated with @TempDir. If the field type or parameter type is neither Path nor File, if a field is declared as final, or if the temporary directory cannot be created, an ExtensionConfigurationException or a ParameterResolutionException will be thrown as appropriate. In addition, a ParameterResolutionException will be thrown for a constructor parameter annotated with @TempDir.


By default, a separate temporary directory is created for every declaration of the @TempDir annotation. If you want to share a temporary directory across all tests in a test class, you should declare the annotation on a static field or on a parameter of a @BeforeAll method.

Old behavior

You can revert to the old behavior of using a single temporary directory by setting the "junit.jupiter.tempdir.scope" configuration parameter to per_context. In that case, the scope of the temporary directory depends on where the first @TempDir annotation is encountered when executing a test class. The temporary directory will be shared by all tests in a class when the annotation is present on a static field or on a parameter of a @BeforeAll method. Otherwise — for example, when @TempDir is only used on instance fields or on parameters in test, @BeforeEach, or @AfterEach methods — each test will use its own temporary directory.

Clean Up

By default, when the end of the scope of a temporary directory is reached, — when the test method or class has finished execution — JUnit will attempt to clean up the temporary directory by recursively deleting all files and directories in the temporary directory and, finally, the temporary directory itself. In case deletion of a file or directory fails, an IOException will be thrown that will cause the test or test class to fail.

The cleanup() attribute allows you to configure the CleanupMode. If the cleanup mode is set to NEVER, the temporary directory will not be cleaned up after the test completes. If the cleanup mode is set to ON_SUCCESS, the temporary directory will only be cleaned up if the test completes successfully. By default, the ALWAYS clean up mode will be used, but this can be configured globally by setting the "junit.jupiter.tempdir.cleanup.mode.default" configuration parameter.

  • Field Details


      @Deprecated @API(status=DEPRECATED, since="5.9") static final String SCOPE_PROPERTY_NAME
      Property name used to set the scope of temporary directories created via @TempDir annotation: "junit.jupiter.tempdir.scope"

      Supported Values

      • per_context: creates a single temporary directory for the entire test class or method, depending on where it's first declared
      • per_declaration: creates separate temporary directories for each declaration site of the @TempDir annotation.

      If not specified, the default is per_declaration.

      See Also:

      @API(status=EXPERIMENTAL, since="5.9") static final String DEFAULT_CLEANUP_MODE_PROPERTY_NAME
      The name of the configuration parameter that is used to configure the default CleanupMode.

      If this configuration parameter is not set, CleanupMode.ALWAYS will be used as the default.

      See Also:
  • Element Details