Introduce BEFORE_METHOD and BEFORE_CLASS modes for @DirtiesContext [SPR-12429]

[spring-projects-issues]

Torsten Krah opened SPR-12429 and commented

Status Quo

@DirtiesContext currently only supports closing a test ApplicationContext after an entire test class or after a test method.

Proposal

It would be useful to have before class and before method modes, too.

Currently this is achievable with a custom TestExecutionListener which marks the context as dirty at the requested phase (before class or before method), but this could be easily achieved via new modes within the @DirtiesContext annotation.

---

Affects: 3.0 GA

Reference URL: http://stackoverflow.com/questions/26931236/is-it-possble-to-reset-spring-tests-context-cache-before-a-test-suite-runs-not

Issue Links:

• BEFORE_* modes in @DirtiesContext cause context to be closed before test [SPR-13180] #17772 BEFORE_* modes in @DirtiesContext cause context to be closed before test

[spring-projects-issues]

Sam Brannen commented

Completed as described in GitHub commit e086a63:

Introduce BEFORE METHOD/CLASS modes in @DirtiesContext

Prior to this commit, @DirtiesContext could only be used to close a
test ApplicationContext after an entire test class or after a test
method; however, there are some use cases for which it would be
beneficial to close a test ApplicationContext before a given test class
or test method -- for example, if some rogue (i.e., yet to be
determined) test within a large test suite has corrupted the original
configuration for the ApplicationContext.

This commit provides a solution to such testing challenges by
introducing the following modes for @DirtiesContext.

• MethodMode.BEFORE_METHOD: configured via the new methodMode attribute

• ClassMode.BEFORE_CLASS and ClassMode.BEFORE_EACH_TEST_METHOD: both
  configured via the existing classMode attribute

[spring-projects-issues]

Sam Brannen commented

FYI: a bug introduced in conjunction with this issue has been fixed in #17772.