title: Using @MockBean in tests forces reloading of Application Context
body: <p>I have several integration tests running on Spring Framework that extend the base class called <em>BaseITCase</em>.<br>
  Like this:</p>
  
  <pre><code>@RunWith(SpringJUnit4ClassRunner.class)
  @ContextConfiguration(classes = {AppCacheConfiguration.class, TestConfiguration.class}, loader = SpringBootContextLoader.class)
  @Transactional
  @WebMvcTest
  public abstract class BaseITCase{...}
  ...
  public class UserControllerTest extends BaseITCase {...}
  </code></pre>
  
  <p>The problem is that one of the test has several declarations of:
  @MockBean inside of it and the moment this test executed, Spring recreates context and the tests that follows this one sometimes use wrong beans(from the context created exactly for the test with @MockBean). I found out about that just by checking that beans have different hashcodes. </p>
  
  <p>It becomes really critical when I use @EventListener. Because listeners for wrong context(context of the test class that has already finished execution) are invoked and I have wrong beans there. </p>
  
  <p>Is there any workaround for that?</p>
  
  <p>I tried to move all @MockBean declarations to basic class and it worked fine because new context is not created. But, it makes basic class too heavy. 
  Also, I tried to make a dirty context for this test, but then the next test fails with message that context has already been closed. </p>