Add a setDirty method to AbstractTestNGSpringContextTests [SPR-5305]

[spring-projects-issues]

Oran Kelly opened SPR-5305 and commented

When using AbstractTestNGSpringContextTests / AbstractTransactionalTestNGSpringContextTests it is not possible to programmatically "dirty" the application context -- the only way to discard the context is via the @DirtiesContext annotation which is at the 'method' level of granularity. As a result it is not (easily) possible to have an application context discarded after all methods in a particular test class have executed.

It would be nice, in a test class that has subclassed AbstractTestNGSpringContextTests, to be able to implement a method such as:

@AfterClass
public void setContextDirty() {
    super.setDirty();
}

... thereby discarding the initialized application context from the TestContextManager's context cache.

---

Affects: 2.5.4

Reference URL: http://forum.springframework.org/showthread.php?t=63592

Issue Links:

• Support for @DirtiesContext at the test class level [SPR-4702] #9379 Support for @DirtiesContext at the test class level

2 votes, 4 watchers

[spring-projects-issues]

Eric Jain commented

Being able to use @DirtiesContext at the class level http://jira.springframework.org/browse/SPR-4702 might be an alternative solution to this problem.

[spring-projects-issues]

Rossen Stoyanchev commented

This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.