如何在没有继承的情况下在我的测试中共享@MockBeans 和模拟方法？

Question

I have a base test scenario that will be used by other integration tests. This scenario includes some mock beans ( @MockBean ) for external integrations.

Today, I have something like this in the integration test class:

@SpringBootTest
@WebAppConfiguration
@DirtiesContext(classMode = DirtiesContext.ClassMode.BEFORE_CLASS)
@RunWith(SpringRunner.class)
@FixMethodOrder(MethodSorters.NAME_ASCENDING)
public class OrderIT {

And the fields and annotations to prepare my integration test:

private MockMvc mockMvc;

@Autowired
private WebApplicationContext wac;

@Autowired
private ObjectMapper mapper;

@MockBean
private SomeGateway someGateway;

@MockBean
private SomeRabbitMqService someRabbitMqService ;

@MockBean
private AnotherRabbitMqService anotherRabbitMqService;

@MockBean
private SomeIntegrationService someIntegrationService ;

@MockBean
private Clock clock;

@Before
public void setup() {
    //some methods mocking each service above, preparing mockMvc, etc
}

This scenario is necessary for use the MockMvc and create the main feature in the system, my Order . This Order is created by calling a POST method in a Rest API, saving the order in a memory database.

Even this working well, I need to duplicate this block of code containing these @MockBean and some @Autowired in another tests, because the Order is the base scenario to add Products to the order, set an Address to deliver, etc. Each scenario has a different integration test but all of them needs an Order .

So, how to share the "MockBeans" and the methods that mocks them among my Integration Tests? I had really bad experiences using inheritance among the tests and I really would like to try a different approach.

Answer 1

I end up using the Spring profiles .

I created a configuration class annotated with @Profile("test") and created the mocked beans there. Like:

@Profile("test")
@Configuration
public class MyMockConfiguration {

    @Bean
    public SomeService someService() {
        SomeService someService = mock(SomeService .class);
        // mocked methods and results
        return someService ;
    }

And in the Test class:

@ActiveProfiles("test")
@SpringBootTest
@WebAppConfiguration
@RunWith(SpringRunner.class)
public class MyControllerIT {

If some integration test needs to override the current mock implementation on the profile, the test just needs to declare @MockBean on the class and proceed on the mock as usual.

I'm not decide yet if test is a good name, because for me makes more sense mock the configuration by "context". So, instead of use the generic name test on the profile name, I could use createOrder and have different configuration profiles, each one with a different name and different mocks: createOrder , createOrderWithoutProducts .

Answer 2

I believe @ContextConfiguration was created for this purpose: https://spring.io/blog/2011/06/21/spring-3-1-m2-testing-with-configuration-classes-and-profiles