单元测试中Mock AVCaptureDeviceInput的问题求助

你遇到的问题本质是方法混淆（Swizzle）破坏了AVFoundation内部的私有逻辑——AVCaptureDevice和AVCaptureDeviceInput的初始化、有效性校验依赖大量未公开的硬件关联逻辑，强行替换方法会导致空值错误、运行时冻结等未定义行为。

更可靠的方案是通过协议抽象+依赖注入解耦业务代码与AVFoundation的具体类，彻底避免对系统类的运行时修改。

步骤1：抽象核心能力协议 #

针对业务中用到的AVCaptureDevice和AVCaptureDeviceInput功能，定义对应协议：

// 抽象摄像头设备的核心属性与方法
protocol CaptureDeviceProtocol {
    var position: AVCaptureDevice.Position { get }
    var deviceType: AVCaptureDevice.DeviceType { get }
    // 按需添加业务中用到的其他方法/属性
}

// 让真实设备类遵循协议
extension AVCaptureDevice: CaptureDeviceProtocol {}

// 抽象摄像头输入的核心能力
protocol CaptureDeviceInputProtocol {
    init(device: CaptureDeviceProtocol) throws
    // 按需添加业务中用到的其他方法
}

// 让真实输入类遵循协议
extension AVCaptureDeviceInput: CaptureDeviceInputProtocol {}

步骤2：修改业务类依赖抽象协议 #

将原来直接依赖AVCaptureDevice和AVCaptureDeviceInput的代码，改为依赖上述协议，并通过构造函数注入实例：

class CameraManager {
    private let device: CaptureDeviceProtocol
    // 注入输入对象的创建工厂，默认使用真实的AVCaptureDeviceInput初始化逻辑
    private let inputFactory: (CaptureDeviceProtocol) throws -> CaptureDeviceInputProtocol
    
    init(
        device: CaptureDeviceProtocol,
        inputFactory: @escaping (CaptureDeviceProtocol) throws -> CaptureDeviceInputProtocol = {
            try AVCaptureDeviceInput(device: $0 as! AVCaptureDevice)
        }
    ) {
        self.device = device
        self.inputFactory = inputFactory
    }
    
    func createCameraInput() throws -> CaptureDeviceInputProtocol {
        return try inputFactory(device)
    }
}

步骤3：创建Mock类用于测试 #

完全自定义Mock实现，模拟各种测试场景：

// Mock摄像头设备
class MockCaptureDevice: CaptureDeviceProtocol {
    var position: AVCaptureDevice.Position
    var deviceType: AVCaptureDevice.DeviceType
    
    init(
        position: AVCaptureDevice.Position = .back,
        deviceType: AVCaptureDevice.DeviceType = .builtInWideAngleCamera
    ) {
        self.position = position
        self.deviceType = deviceType
    }
}

// Mock摄像头输入
class MockCaptureDeviceInput: CaptureDeviceInputProtocol {
    let device: CaptureDeviceProtocol
    var shouldThrowError = false
    
    required init(device: CaptureDeviceProtocol) throws {
        self.device = device
        // 模拟初始化失败场景
        if shouldThrowError {
            throw NSError(domain: "MockError", code: -1, userInfo: [NSLocalizedDescriptionKey: "初始化失败"])
        }
    }
}

步骤4：编写单元测试 #

通过Mock类轻松覆盖各种场景：

import XCTest
@testable import YourApp

class CameraManagerTests: XCTestCase {
    func testCreateInputSuccess() throws {
        // 准备Mock设备
        let mockDevice = MockCaptureDevice(position: .front)
        // 准备Mock输入工厂
        let mockInputFactory: (CaptureDeviceProtocol) throws -> CaptureDeviceInputProtocol = { device in
            return try MockCaptureDeviceInput(device: device)
        }
        
        let manager = CameraManager(device: mockDevice, inputFactory: mockInputFactory)
        let input = try manager.createCameraInput()
        
        // 验证结果
        XCTAssertTrue(input is MockCaptureDeviceInput)
        XCTAssertEqual((input as! MockCaptureDeviceInput).device.position, .front)
    }
    
    func testCreateInputFailure() throws {
        let mockDevice = MockCaptureDevice()
        // 模拟初始化失败的工厂
        let failingInputFactory: (CaptureDeviceProtocol) throws -> CaptureDeviceInputProtocol = { device in
            let mockInput = MockCaptureDeviceInput(device: device)
            mockInput.shouldThrowError = true
            throw mockInput.shouldThrowError ? NSError(domain: "MockError", code: -1, userInfo: nil) : nil
        }
        
        let manager = CameraManager(device: mockDevice, inputFactory: failingInputFactory)
        
        // 验证是否抛出预期错误
        XCTAssertThrowsError(try manager.createCameraInput()) { error in
            XCTAssertEqual((error as NSError).code, -1)
        }
    }
}

为什么这个方案更优 #

1. 无运行时副作用：完全避免修改系统类的内部实现，不会触发AVFoundation的私有校验逻辑
2. 代码解耦：业务类不再强依赖AVFoundation，后续替换摄像头框架更容易
3. 场景全覆盖：Mock类可以灵活模拟成功、失败、不同设备属性等各种测试场景

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