anchor.diff:  include::{testDir}/example/TempDirectoryDemo.java[tags=user_guide]
   ----
   
  -In addition to the default file system, the extension can be used with any `FileSystem`
  -implementation, e.g. https://github.com/google/jimfs[Jimfs]. In order to use a custom file
  -system, simply register the extension programmatically and pass a provider of a custom
  -parent directory of type `Path`. The following example uses the Jimfs `FileSystem` and
  -passes a custom `tmp` parent directory to the `createInCustomDirectory` static factory
  -method.
  +In addition to the default file system for the local operating system, the
  +`TempDirectory` extension can also be used with any `FileSystem` implementation -- for
  +example, https://github.com/google/jimfs[Jimfs]. In order to use a custom file system,
  +register the extension _programmatically_ via `@RegisterExtension` and supply a provider
  +of a custom parent directory of type `Path`. The following example uses the Jimfs
  +`FileSystem` and passes a custom `tmp` parent directory to the
  +`createInCustomDirectory()` static factory method.
   
   [source,java]
  -.A test class that sets up the TempDirectory extension to use a custom file system
  +.A test class that configures the TempDirectory extension to use a custom file system
   ----
   include::{testDir}/example/TempDirectoryWithCustomFileSystemDemo.java[tags=user_guide]
   ----
  
positive.code: `@DisabledOnOs`, etc.) even when the "per-method" test instance lifecycle mode is active.
  
  If you would prefer that JUnit Jupiter execute all test methods on the same test
  instance, simply annotate your test class with `@TestInstance(Lifecycle.PER_CLASS)`. When
  using this mode, a new test instance will be created once per test class. Thus, if your
  test methods rely on state stored in instance variables, you may need to reset that state
  in `@BeforeEach` or `@AfterEach` methods.
  
  The "per-class" mode has some additional benefits over the default "per-method" mode.
  Specifically, with the "per-class" mode it becomes possible to declare `@BeforeAll` and
  
negative.code: [[writing-tests-repeated-tests]]
  === Repeated Tests
  
  JUnit Jupiter provides the ability to repeat a test a specified number of times by
  annotating a method with `@RepeatedTest` and specifying the total number of repetitions
  desired. Each invocation of a repeated test behaves like the execution of a regular
  `@Test` method with full support for the same lifecycle callbacks and extensions.
  