Visualize the problem with @DirtiesContext

[rieckpil]

Referring to the question on StackOverflow

if you now run ./gradlew test -i --rerun-tasks without the use of @DirtiesContext you should see the following:

JMSConsumerIntegrationTest > shouldInvokeRepositoryWhenGreetedWithASpecificMessage() STANDARD_OUT
    --- Send from context: org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@3b776a76, started on Mon Jun 22 08:33:50 CEST 2020
    --- Consumed by context: org.springframework.web.context.support.GenericWebApplicationContext@235dfc4d, started on Mon Jun 22 08:33:48 CEST 2020

with using @DirtiesContext and therefore shutting down application contexts from the previous tests:

JMSConsumerIntegrationTest > shouldInvokeRepositoryWhenGreetedWithASpecificMessage() STANDARD_OUT
    Sending message in context: org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@35828e64, started on Mon Jun 22 08:21:17 CEST 2020
    consumed!
    org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@35828e64, started on Mon Jun 22 08:21:17 CEST 2020

With the second commit, you are now able to run all tests together without the need for @DirtiesContext.

[ajaydivakaran]

@rieckpil Thanks for taking the time to do this.

[rieckpil]

you are welcome @ajaydivakaran 👍