anchor.diff:  @AfterAll AbstractDatabaseTests.destroyDatabase()
   ----
   
  -The following sequence diagram helps to shed further light on actually what goes on within
  +The following sequence diagram helps to shed further light on what actually goes on within
   the `JupiterTestEngine` when the `DatabaseTestsDemo` test class is executed.
   
   ////
  
positive.code: 
  See corresponding *.txt file in images folder for the source.
  ////
  image::extensions_DatabaseTestsDemo.png[caption='',title='DatabaseTestsDemo.java']
  
  JUnit Jupiter does **not** guarantee the order in which multiple lifecycle methods are
  invoked within a _single_ test class. It would appear that JUnit Jupiter invokes such
  
negative.code: === 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-supplied test and lifecycle methods. The
  following diagram illustrates the relative order of user-supplied code and extension code.
  
  ==== User and Extension Code
  
  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
  
  