如何解决LocalBroadcastManager无法被Mockito Mock的单元测试问题？

确实踩过这个坑！LocalBroadcastManager被标成final类，Mockito默认没法直接Mock或Spy它，下面给你几个靠谱的解决办法，从快速临时方案到长期优雅架构优化都有：

适合不想改动原有业务代码的场景，快速搞定测试需求。

1. 先添加PowerMock依赖（注意和你的Mockito版本兼容，以下是适配Mockito2的示例）：

testImplementation 'org.powermock:powermock-module-junit4:2.0.9'
testImplementation 'org.powermock:powermock-api-mockito2:2.0.9'

2. 在测试类上添加注解，告诉PowerMock要处理LocalBroadcastManager这个final类：

@RunWith(PowerMockRunner.class)
@PrepareForTest(LocalBroadcastManager.class)
public class YourTargetClassTest {
    // 测试代码写在这里
}

3. 正常Mock并验证广播发送逻辑：

@Mock
private LocalBroadcastManager mockLbm;
private YourTargetClass targetClass;
private Context mockContext;

@Before
public void setUp() {
    MockitoAnnotations.initMocks(this);
    PowerMockito.mockStatic(LocalBroadcastManager.class);
    // 让getInstance返回我们的Mock对象
    PowerMockito.when(LocalBroadcastManager.getInstance(mockContext)).thenReturn(mockLbm);
    targetClass = new YourTargetClass(mockContext);
}

@Test
public void testBroadcastSentWithCorrectExtras() {
    // 触发业务逻辑中发送广播的条件
    targetClass.triggerBroadcastCondition();

    // 捕获发送的Intent，验证内容
    ArgumentCaptor<Intent> intentCaptor = ArgumentCaptor.forClass(Intent.class);
    verify(mockLbm).sendBroadcast(intentCaptor.capture());
    Intent sentIntent = intentCaptor.getValue();
    
    assertEquals("com.your.app.TARGET_ACTION", sentIntent.getAction());
    assertEquals("expected_extra_value", sentIntent.getStringExtra("extra_key"));
    // 按需验证其他Extras参数
}

⚠️ 注意：PowerMock会让测试逻辑变重，且要注意版本兼容性，避免和其他测试库冲突。

通过重构代码解耦对LocalBroadcastManager的直接依赖，不仅解决测试问题，还让代码更符合面向接口设计原则。

1. 定义一个广播发送的抽象接口：

public interface BroadcastDispatcher {
    void sendBroadcast(Intent intent);
}

2. 实现基于LocalBroadcastManager的具体类：

public class LocalBroadcastDispatcher implements BroadcastDispatcher {
    private final LocalBroadcastManager lbm;

    public LocalBroadcastDispatcher(Context context) {
        this.lbm = LocalBroadcastManager.getInstance(context);
    }

    @Override
    public void sendBroadcast(Intent intent) {
        lbm.sendBroadcast(intent);
    }
}

3. 修改业务类，通过构造函数注入BroadcastDispatcher：

public class YourTargetClass {
    private final BroadcastDispatcher broadcastDispatcher;

    // 构造函数注入，测试时可传入Mock对象
    public YourTargetClass(BroadcastDispatcher broadcastDispatcher) {
        this.broadcastDispatcher = broadcastDispatcher;
    }

    public void triggerBroadcastCondition() {
        Intent intent = new Intent("com.your.app.TARGET_ACTION");
        intent.putExtra("extra_key", "expected_extra_value");
        broadcastDispatcher.sendBroadcast(intent);
    }
}

4. 测试时直接Mock抽象接口，完全不用管LocalBroadcastManager：

@Mock
private BroadcastDispatcher mockDispatcher;
private YourTargetClass targetClass;

@Before
public void setUp() {
    MockitoAnnotations.initMocks(this);
    targetClass = new YourTargetClass(mockDispatcher);
}

@Test
public void testBroadcastContent() {
    targetClass.triggerBroadcastCondition();

    ArgumentCaptor<Intent> intentCaptor = ArgumentCaptor.forClass(Intent.class);
    verify(mockDispatcher).sendBroadcast(intentCaptor.capture());
    Intent sentIntent = intentCaptor.getValue();

    assertEquals("com.your.app.TARGET_ACTION", sentIntent.getAction());
    assertEquals("expected_extra_value", sentIntent.getStringExtra("extra_key"));
}

这个方案的好处是代码解耦，后续如果换用其他事件传递方式（比如LiveData、EventBus），只需要替换BroadcastDispatcher的实现类，业务代码完全不用改。

如果不想用PowerMock也不想改代码，还可以直接用真实的LocalBroadcastManager，在测试中注册临时接收器捕获广播内容。

private Context testContext;
private LocalBroadcastManager lbm;
private YourTargetClass targetClass;
private Intent capturedIntent;

@Before
public void setUp() {
    testContext = ApplicationProvider.getApplicationContext();
    lbm = LocalBroadcastManager.getInstance(testContext);
    targetClass = new YourTargetClass(testContext);

    // 注册测试用的广播接收器
    BroadcastReceiver testReceiver = new BroadcastReceiver() {
        @Override
        public void onReceive(Context context, Intent intent) {
            capturedIntent = intent;
        }
    };
    lbm.registerReceiver(testReceiver, new IntentFilter("com.your.app.TARGET_ACTION"));
}

@After
public void tearDown() {
    // 测试结束注销接收器，避免内存泄漏
    lbm.unregisterReceiver(testReceiver);
}

@Test
public void testBroadcastExtras() {
    targetClass.triggerBroadcastCondition();

    // 验证捕获到的Intent
    assertNotNull(capturedIntent);
    assertEquals("com.your.app.TARGET_ACTION", capturedIntent.getAction());
    assertEquals("expected_extra_value", capturedIntent.getStringExtra("extra_key"));
}

这个方式用的是真实组件，属于偏集成测试的思路，但因为LocalBroadcastManager是内存内的，测试速度依然很快。

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