Spring Test should not modify the application context under test [SPR-8503]

[spring-projects-issues]

Neale Upstone opened SPR-8503 and commented

When using @ContextConfiguration in a test @Autowired annotated fields get wired, even if context:annotation-driven/ has not been specified.

This is incorrect behaviour, as it means that a test can pass against a context configuration which when used in production will not behave that way.

A better approach would be to load the specified configuration into one application context, and then use a child context for wiring the test fixture.

The child context can then have the additional post processors, without polluting the application context under test.

---

Affects: 3.1 M2

Issue Links:

• Load dedicated child ApplicationContext for test instance in the TestContext framework [SPR-4632] #9309 Load dedicated child ApplicationContext for test instance in the TestContext framework ("duplicates")

[spring-projects-issues]

Neale Upstone commented

As a workaround, here's my recommendation for what to do for your application contexts in Spring 3.0 and earlier.

public class RepositoryContextLoadTest {
	
	private static final String[] locations = {"classpath:/fuzzy-repository-context.xml"};

	@Test 
	public void matchesForAPersonAreInOrder(){
		GenericXmlApplicationContext context = new GenericXmlApplicationContext();
		context.load(locations);
		context.refresh();
		context.start();
		
		FuzzyRepository<?> repo = context.getBean(FuzzyRepository.class);
		assertNotNull(repo);
		
		context.close();
	}
}

[spring-projects-issues]

Neale Upstone commented

(If only I could edit my own comment: the name of the test method shouldn't be my quick copy pasted one ;) )

[spring-projects-issues]

Sam Brannen commented

Duplicate of #9309.