anchor.diff:  ----
   
   Note that this feature lets test dependencies be `final` and therefore immutable.
  +
  +If the `spring.test.constructor.autowire` property is to `true` (see
  +<<integration-testing-annotations-testconstructor>>), we can omit the declaration of
  +`@Autowired` on the constructor in the previous example resulting in the following.
  +
  +[source,java,indent=0]
  +[subs="verbatim,quotes"]
  +----
  +	@SpringJUnitConfig(TestConfig.class)
  +	class OrderServiceIntegrationTests {
  +
  +		private final OrderService orderService;
  +
  +		OrderServiceIntegrationTests(OrderService orderService) {
  +			this.orderService = orderService.
  +		}
  +
  +		// tests that use the injected OrderService
  +	}
  +----
   
   [[testcontext-junit-jupiter-di-method]]
   ====== Method Injection
  
positive.code: [[testcontext-junit-jupiter-di-constructor]]
  ====== Constructor Injection
  
  If a parameter in a constructor for a JUnit Jupiter test class is of type
  `ApplicationContext` (or a sub-type thereof) or is annotated or meta-annotated with
  `@Autowired`, `@Qualifier`, or `@Value`, Spring injects the value for that specific
  parameter with the corresponding bean from the test's `ApplicationContext`. You can also
  directly annotate a test constructor with `@Autowired` if all of the parameters should be
  supplied by Spring.
  
  WARNING: If the constructor for a test class is itself annotated with `@Autowired`,
  Spring assumes the responsibility for resolving _all_ parameters in the constructor.
  Consequently, no other `ParameterResolver` registered with JUnit Jupiter can resolve
  parameters for such a constructor.
  
  
negative.code: 
  * <<integration-testing-annotations-junit-jupiter-springjunitconfig>>
  * <<integration-testing-annotations-junit-jupiter-springjunitwebconfig>>
  * <<integration-testing-annotations-testconstructor>>
  * <<integration-testing-annotations-junit-jupiter-enabledif>>
  * <<integration-testing-annotations-junit-jupiter-disabledif>>
  
  