anchor.diff:  
   If a method within a test class is annotated with `@PostConstruct`, that method will be
   executed before any __before__ methods of the underlying test framework (e.g., methods
  -annotated with JUnit 4's `@Before`), and that will apply for every test method in the test
  -class. On the other hand, if a method within a test class is annotated with
  +annotated with JUnit Jupiter's `@BeforeEach`), and that will apply for every test method
  +in the test class. On the other hand, if a method within a test class is annotated with
   `@PreDestroy`, that method will __never__ be executed. Within a test class it is
   therefore recommended to use test lifecycle callbacks from the underlying test framework
   instead of `@PostConstruct` and `@PreDestroy`.
   ====
   
   
  -[[integration-testing-annotations-junit]]
  +[[integration-testing-annotations-junit4]]
   ==== Spring JUnit 4 Testing Annotations
  +
   The following annotations are __only__ supported when used in conjunction with the
   <<testcontext-junit4-runner,SpringRunner>>, <<testcontext-junit4-rules,Spring's JUnit
  -rules>>, or <<testcontext-support-classes-junit4,Spring's JUnit 4 support classes>>.
  +4 rules>>, or <<testcontext-support-classes-junit4,Spring's JUnit 4 support classes>>.
   
   ===== @IfProfileValue
   `@IfProfileValue` indicates that the annotated test is enabled for a specific testing
  
positive.code: 	public class UserRepositoryTests { }
  ----
  
  We can reduce the above duplication by introducing a custom _composed annotation_
  that centralizes the common test configuration like this:
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  
negative.code: [[testcontext-tx-annotation-demo]]
  ===== Demonstration of all transaction-related annotations
  
  The following JUnit 4 based example displays a _fictitious_ integration testing scenario
  highlighting all transaction-related annotations. The example is **not** intended to
  demonstrate best practices but rather to demonstrate how these annotations can be used.
  Consult the <<integration-testing-annotations,annotation support>> section for further
  