使用MockIntegration替换ImapIdleChannelAdapter报Bean类型不匹配异常解决

你遇到的类型不匹配异常来自两个核心错误：

1. 方法用错了：ImapIdleChannelAdapter是事件驱动的MessageProducer实现，不属于轮询模式的SourcePollingChannelAdapter。你调用的substituteMessageSourceFor方法仅支持替换轮询类入站适配器，会强制把目标Bean转为SourcePollingChannelAdapter，必然抛出类型不匹配错误。
2. Bean名称匹配错误：你没有给ImapIdleChannelAdapter的@Bean显式指定名称，默认Bean名是配置类里的方法名getAdapter，既不是你写在noAutoStartup里的inboundChannelAdapter，也不是替换时传入的imapIdleChannelAdapter，就算方法选对了也会找不到目标Bean。

1. 调整生产配置，显式指定适配器Bean名称 #

给IMAP适配器的@Bean注解显式命名，同时保证测试阶段的禁止自动启动规则能命中它，避免测试启动时真实适配器连接邮箱：

public class ImapConfiguration{

    @Bean
    ImapMailReceiver getReceiver() {
        ImapMailReceiver receiver = new ImapMailReceiver(ImapConfig.getUri());
        return receiver;
    }

    @Bean("imapIdleAdapter") // 显式指定Bean名称，方便测试定位
    ImapIdleChannelAdapter getAdapter(ImapMailReceiver receiver) {
        ImapIdleChannelAdapter adapter = new InternalImapIdleChannelAdapter(receiver);
        adapter.setAutoStartup(true);
        return adapter;
    }

    @Bean
    StandardIntegrationFlow getFlow(ImapIdleChannelAdapter adapter, GenericHandler handler) {
        return IntegrationFlows.from(adapter)
                .handle(handler)
                .get();
    }
}

2. 调整测试类配置，使用对应类型的Mock替换方法 #

针对MessageProducer类型的端点，使用substituteMessageProducerFor方法替换，配合MockIntegration.mockMessageProducer()构造Mock对象，主动发送测试消息模拟邮件到达事件：

@SpringBootTest(classes = ImapConfiguration.class)
@Import({ReceiverTestConf.class})
// 这里的noAutoStartup匹配刚才显式指定的Bean名
@SpringIntegrationTest(noAutoStartup = "imapIdleAdapter")
public class ImapMailReceiverTest {
    
    @Captor
    ArgumentCaptor<ReceivedMail> emailCaptor = ArgumentCaptor.forClass(ReceivedMail.class);
    
    @MockBean
    TestEmailHandler emailHandlerTestImpl;
    
    @Autowired
    TestImapReceiver imapReceiver;
    
    @Autowired
    MockIntegrationContext mockIntegrationContext;
    
    @Test
    @SneakyThrows
    void receive() throws MessagingException {
        Mockito.doNothing().when(emailHandlerTestImpl).handle(Mockito.any());
        
        // 构造Mock消息生产者
        MessageProducer mockImapProducer = MockIntegration.mockMessageProducer().getObject();
        // 用生产者专用的替换方法替换真实的IMAP适配器
        mockIntegrationContext.substituteMessageProducerFor("imapIdleAdapter", mockImapProducer);
        
        // 启动Mock生产者
        mockImapProducer.start();
        
        // 构造测试用MimeMessage，模拟收到邮件
        MimeMessage testMail = buildTestMimeMessage();
        // 往Mock生产者发送测试消息，触发下游流处理
        mockImapProducer.sendMessage(new GenericMessage<>(testMail));
        
        await().atMost(1, TimeUnit.SECONDS).untilAsserted(() -> {
                Mockito.verify(emailHandlerTestImpl, Mockito.times(1)).handle(emailCaptor.capture());
                List<ReceivedMail> result = emailCaptor.getAllValues();
                Assertions.assertEquals(1, result.size());
            }
        );
    }

    // 构造测试MimeMessage的工具方法
    private MimeMessage buildTestMimeMessage() throws MessagingException {
        Session session = Session.getInstance(new Properties());
        MimeMessage message = new MimeMessage(session);
        message.setFrom(new InternetAddress("sender@test.com"));
        message.setRecipient(Message.RecipientType.TO, new InternetAddress("receiver@test.com"));
        message.setSubject("Test Mail");
        message.setText("Test content");
        return message;
    }
}

Spring Integration测试中替换端点需要严格匹配端点类型：

• 轮询类入站端点（如搭配FileReadingMessageSource的SourcePollingChannelAdapter）使用substituteMessageSourceFor
• 事件驱动类入站端点（如ImapIdleChannelAdapter、各类MQ入站适配器）使用substituteMessageProducerFor
• 出站处理器使用substituteMessageHandlerFor

所有需要Mock的集成端点，建议在@Bean注解上显式指定名称，避免默认方法名和预期不一致导致替换失败。

内容的提问来源于stack exchange，提问作者Pewpew