anchor.diff:  JUnit 4, the JUnit 5 extension model consists of a single, coherent concept: the
   `Extension` API. Note, however, that `Extension` itself is just a marker interface.
   
  +[[extension-registration]]
   === Registering Extensions
   
   Extensions can be registered either declaratively via `{ExtendWith}` or programmatically
  
positive.code: 
  Note that registered extensions are inherited within test class hierarchies.
  
  ==== Declarative Extension Registration
  
  Developers can register one or more extensions _declaratively_ by annotating a test
  
negative.code: If a `@Test`, `@BeforeEach`, `@AfterEach` , `@BeforeAll` or `@AfterAll` method accepts a
  parameter, the parameter must be _resolved_ at runtime by a `MethodParameterResolver`. A
  `MethodParameterResolver` can either be built-in (see `{TestInfoParameterResolver}`) or
  <<extension-registration,registered by the user>>. Generally speaking, parameters may be
  resolved by _name_, _type_, _annotation_, or any combination thereof. For concrete examples,
  consult the source code for `{CustomTypeParameterResolver}` and
  `{CustomAnnotationParameterResolver}`.
  
  === Test Lifecycle Callbacks
  
  