anchor.diff:  
   It supports both the link:https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/RegisterExtension.html[@RegisterExtension^] and link:https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExtendWith.html[@ExtendWith^] annotations.
   
  -When using `@RegisterExtension`, the extensions can be customized further:
  +When using link:https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/RegisterExtension.html[@RegisterExtension^], the extensions can be customized further:
   
   [source,java]
   ----
  
positive.code: }
  ----
  
  The instances injected are the same instances as returned by `getJdbi()` and `getSharedHandle()`.
  
  The javadoc for link:{jdbidocs}/testing/junit5/JdbiExtension.html[JdbiExtension] contains further information on how to customize a programmatically registered instance.
  
  
  == Third-Party Integration
  
negative.code: }
  ----
  
  [NOTE]
  link:{jdbidocs}/testing/junit5/JdbiExtension.html[JdbiExtension^] and all the database specific subclasses are intended to be registered as instance fields. Fields annotated with the link:https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/RegisterExtension.html[@RegisterExtension^] that hold JdbiExtension instances should *not* be static! While this may work, the behavior is currently undefined and should be avoided.
  
  The javadoc page for link:{jdbidocs}/testing/junit5/JdbiExtension.html[JdbiExtension^] contains additional information on how to customize a programmatically registered instance.
  
  When using the link:https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExtendWith.html[@ExtendWith^] declarative extension, test methods can access the link:{jdbidocs}/core/Jdbi.html[Jdbi^] and link:{jdbidocs}/core/Handle.html[Handle^] objects through method parameters:
  
  [source,java]
  ----
  