Test annotation to indicate that a test method dirties the context
for the current test.
Using this annotation in conjunction with
AbstractAnnotationAwareTransactionalTests is less error-prone than
calling
setDirty()
explicitly because the call to setDirty() is guaranteed to
occur, even if the test failed. If only a particular code path in the test
dirties the context, prefer calling setDirty() explicitly --
and take care!
Test annotation to indicate that a test method dirties the context for the current test.
Using this annotation in conjunction with AbstractAnnotationAwareTransactionalTests is less error-prone than calling setDirty() explicitly because the call to
setDirty()is guaranteed to occur, even if the test failed. If only a particular code path in the test dirties the context, prefer callingsetDirty()explicitly -- and take care!