anchor.diff:  === Relative Execution Order of User Code and Extensions
   
   When executing a test class that contains one or more test methods, a number of extension
  -callbacks are called in addition to the user-provided test and lifecycle methods. The
  -following diagrams illustrates the relative order of user-provided code and extension code.
  +callbacks are called in addition to the user-supplied test and lifecycle methods. The
  +following diagram illustrates the relative order of user-supplied code and extension code.
   
   ==== User and Extension Code
   
  -User-provided test and lifecycle methods are shown in orange, with callback code provided
  -by extensions shown in blue. The grey box denotes the execution of a single test method
  -and will be repeated for every test method in the test class.
  +User-supplied test and lifecycle methods are shown in orange, with callback code
  +implemented by extensions shown in blue. The grey box denotes the execution of a single
  +test method and will be repeated for every test method in the test class.
   
   :figure-caption: User code and extension code
   
  
positive.code: callbacks implemented by `Extension2`. `Extension1` is therefore said to _wrap_
  `Extension2`.
  
  JUnit Jupiter also guarantees _wrapping_ behavior within class hierarchies for
  user-supplied lifecycle callbacks such as `@BeforeAll`, `@AfterAll`, `@BeforeEach`, and
  `@AfterEach`.
  
  The following examples demonstrate this behavior. Please note that the examples do not
  actually do anything realistic. Instead, they mimic common scenarios for testing
  
negative.code: @AfterAll AbstractDatabaseTests.destroyDatabase()
  ----
  
  The following sequence diagram helps to shed further light on what actually goes on within
  the `JupiterTestEngine` when the `DatabaseTestsDemo` test class is executed.
  
  ////
  