Android单元测试实践指南：从基础到高级技巧

1. Android单元测试概述在移动应用开发领域Android单元测试是保证代码质量的基础防线。作为一名经历过多个商业项目的老兵我深刻体会到单元测试对项目长期维护的价值。不同于集成测试或UI测试单元测试聚焦于验证最小可测试单元通常是单个方法或类的正确性具有执行速度快、定位问题精准的特点。Android单元测试主要分为两类本地单元测试运行在JVM上和仪器化测试需要Android设备或模拟器。本地测试适合纯Java逻辑验证而仪器化测试则用于需要Android框架支持的场景。实际项目中我们通常会混合使用这两种方式构建完整的测试金字塔。提示新手常犯的错误是过度依赖UI测试而忽视单元测试。实际上单元测试应该占测试套件的70%以上因为它们运行更快、维护成本更低。2. 测试环境搭建与工具选型2.1 基础工具链配置Android Studio默认已集成JUnit测试框架但完整的测试生态还需要以下依赖dependencies { // 本地单元测试 testImplementation junit:junit:4.13.2 testImplementation org.mockito:mockito-core:4.5.1 // 仪器化测试 androidTestImplementation androidx.test:runner:1.4.0 androidTestImplementation androidx.test.espresso:espresso-core:3.4.0 androidTestImplementation androidx.test.ext:junit:1.1.3 }Mockito是模拟依赖的利器而Espresso则适合UI交互测试。对于更复杂的场景可以考虑添加TruthGoogle提供的流畅断言库Robolectric在JVM上模拟Android运行环境UI Automator跨应用UI测试框架2.2 测试目录结构规范标准的Android项目测试目录如下src/ ├── main/ # 主代码 ├── test/ # 本地单元测试 └── androidTest/ # 仪器化测试我习惯按功能模块组织测试类例如test/ └── com/example/ └── feature/ ├── auth/ │ ├── LoginValidatorTest.kt │ └── TokenManagerTest.kt └── payment/ ├── CurrencyConverterTest.kt └── PaymentProcessorTest.kt3. 核心测试模式与实践3.1 基本单元测试编写一个典型的JUnit测试类结构如下class CalculatorTest { private lateinit var calculator: Calculator Before fun setUp() { calculator Calculator() } Test fun addition should return correct sum() { // Given val a 5 val b 3 // When val result calculator.add(a, b) // Then assertEquals(8, result) } Test(expected IllegalArgumentException::class) fun division by zero should throw exception() { calculator.divide(10, 0) } }注意测试方法命名推荐使用反引号包裹的描述性名称Kotlin特性这比传统的testAdd()更易读。3.2 模拟依赖的进阶技巧当测试对象依赖外部服务或复杂组件时使用Mockito进行模拟Test fun login should call network service() { // 创建模拟对象 val mockService mock(NetworkService::class.java) val authManager AuthManager(mockService) // 设置模拟行为 when(mockService.login(user, pass)).thenReturn(true) // 执行测试 val result authManager.attemptLogin(user, pass) // 验证交互 assertTrue(result) verify(mockService).login(user, pass) }对于Android组件可以使用AndroidX Test提供的组件RunWith(AndroidJUnit4::class) class SharedPreferencesTest { private lateinit var context: Context Before fun setup() { context ApplicationProvider.getApplicationContext() } Test fun should save user preference() { val prefs context.getSharedPreferences(test, Context.MODE_PRIVATE) prefs.edit().putString(theme, dark).apply() assertEquals(dark, prefs.getString(theme, null)) } }4. 复杂场景测试策略4.1 异步代码测试处理RxJava或协程的测试需要特殊技巧Test fun fetch data from network() runBlockingTest { // Given val mockApi mock(ApiService::class.java) when(mockApi.getData()).thenReturn(Response.success(TestData)) // When val repository DataRepository(mockApi) val result repository.loadData() // Then assertEquals(TestData, result) }对于LiveData测试OptIn(ExperimentalCoroutinesApi::class) Test fun liveData should emit values() runTest { val liveData MutableLiveDataString() val observer ObserverString { /* 可记录值 */ } liveData.observeForever(observer) liveData.postValue(test) advanceUntilIdle() // 确保协程执行完成 assertEquals(test, liveData.value) liveData.removeObserver(observer) }4.2 数据库与文件操作测试使用Room数据库测试时推荐内存数据库RunWith(AndroidJUnit4::class) class UserDaoTest { private lateinit var database: AppDatabase private lateinit var dao: UserDao Before fun createDb() { val context ApplicationProvider.getApplicationContextContext() database Room.inMemoryDatabaseBuilder(context, AppDatabase::class.java) .allowMainThreadQueries() .build() dao database.userDao() } After fun closeDb() { database.close() } Test fun insert and query user() { val user User(id 1, name test) dao.insert(user) val loaded dao.getById(1) assertEquals(user.name, loaded?.name) } }5. 测试覆盖率与持续集成5.1 生成测试覆盖率报告在build.gradle中配置Jacocoandroid { buildTypes { debug { testCoverageEnabled true } } } // 添加jacoco插件 apply plugin: jacoco task jacocoTestReport(type: JacocoReport, dependsOn: [testDebugUnitTest]) { reports { xml.enabled true html.enabled true } sourceDirectories.setFrom(files($projectDir/src/main/java)) executionData.setFrom(fileTree(dir: $buildDir, includes: [ jacoco/testDebugUnitTest.exec, outputs/code-coverage/connected/*coverage.ec ])) }执行./gradlew jacocoTestReport后报告会生成在build/reports/jacoco/目录下。5.2 CI/CD集成策略在GitHub Actions中的典型配置name: Android CI on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkoutv2 - name: Set up JDK uses: actions/setup-javav2 with: java-version: 11 distribution: temurin - name: Run unit tests run: ./gradlew testDebugUnitTest - name: Run instrumented tests uses: reactivecircus/android-emulator-runnerv2 with: api-level: 30 script: ./gradlew connectedDebugAndroidTest6. 常见问题与性能优化6.1 测试速度提升技巧使用静态模拟替换动态Mockito.mock()为手动实现的轻量模拟类避免PowerMock改用Mockito-inline处理final类/方法并行执行在gradle.properties中添加org.gradle.paralleltrue org.gradle.workers.max4过滤慢测试使用Category标记慢测试单独运行6.2 测试维护难题问题UI测试随界面变化频繁失败解决方案为View添加测试IDandroid:idid/loginButton使用页面对象模式class LoginPage { fun enterUsername(text: String) { onView(withId(R.id.usernameField)) .perform(typeText(text)) } fun clickLogin() { onView(withId(R.id.loginButton)) .perform(click()) } }问题测试数据管理混乱解决方案建立测试数据工厂object TestDataFactory { fun createUser( id: Int Random.nextInt(), name: String user_${Random.nextInt()} ) User(id, name) }7. 高级测试架构模式7.1 测试驱动开发(TDD)实践TDD的标准流程编写一个失败的测试实现最小可通过的代码重构代码保持测试通过示例开发一个字符串计算器// 步骤1编写测试 Test fun empty string should return zero() { assertEquals(0, StringCalculator.add()) } // 步骤2实现最简单代码 class StringCalculator { companion object { fun add(numbers: String): Int { return 0 } } } // 步骤3添加更多测试用例 Test fun single number returns its value() { assertEquals(5, StringCalculator.add(5)) } // 步骤4扩展实现 fun add(numbers: String): Int { if (numbers.isEmpty()) return 0 return numbers.toInt() }7.2 面向契约测试使用Pact进行消费者驱动契约测试Pact(consumer AndroidApp) fun androidAppPact(builder: PactDslWithProvider): RequestResponsePact { return builder .given(user exists) .uponReceiving(request for user) .path(/users/123) .method(GET) .willRespondWith() .status(200) .body( PactDslJsonBody() .integerType(id, 123) .stringType(name, test user) ) .toPact() } PactVerification(fragment androidAppPact) Test fun verify user api contract() { val response apiClient.getUser(123) assertEquals(200, response.code()) assertEquals(test user, response.body()?.name) }8. 测试代码质量保障8.1 测试代码审查要点独立性测试之间不应有依赖可读性遵循Given-When-Then模式确定性相同输入总是产生相同结果单一职责每个测试只验证一个行为真实性避免过度模拟导致虚假通过8.2 测试代码重构技巧坏味道测试方法过长重构提取辅助方法// 重构前 Test fun complex order calculation() { val order Order().apply { addItem(Item(price 100, quantity 2)) addItem(Item(price 50, quantity 3)) applyCoupon(Coupon(discount 10, type PERCENT)) setShipping(Shipping(method express, cost 20)) } assertEquals(270, order.totalPrice) } // 重构后 Test fun order total with discount and shipping() { val order createTestOrder( items listOf( testItem(100, 2), testItem(50, 3) ), coupon testCoupon(10, PERCENT), shipping testShipping(express, 20) ) assertEquals(270, order.totalPrice) }坏味道重复测试数据重构使用工厂方法或测试夹具object TestFixtures { fun validUser() User( id 1, name test, email testexample.com ) fun expiredToken() Token( value expired, expiresAt Instant.now().minus(1, ChronoUnit.HOURS) ) }9. 测试报告与可视化9.1 自定义HTML报告使用Gradle测试日志配置android { testOptions { unitTests.all { testLogging { events passed, skipped, failed, standardOut, standardError showExceptions true exceptionFormat full showCauses true showStackTraces true afterSuite { desc, result - if (!desc.parent) { def output Results: ${result.resultType} (${result.testCount} tests, ${result.successfulTestCount} passed, ${result.failedTestCount} failed, ${result.skippedTestCount} skipped) println(output) } } } } } }9.2 使用SonarQube分析配置sonar-project.propertiessonar.projectKeyandroid_app sonar.projectNameMy Android App sonar.projectVersion1.0 sonar.sourcessrc/main/java sonar.testssrc/test/java,src/androidTest/java sonar.java.binariesbuild/intermediates/javac/debug/classes sonar.junit.reportPathsbuild/test-results/testDebugUnitTest sonar.jacoco.reportPathsbuild/jacoco/testDebugUnitTest.exec sonar.android.lint.reportPathsbuild/reports/lint-results.xml10. 跨模块测试策略10.1 模块间接口测试对于多模块项目建议在基础模块定义契约接口各实现模块提供测试桩核心业务模块针对接口测试// 基础模块 interface AnalyticsService { fun logEvent(event: String) } // 实现模块 class FirebaseAnalytics : AnalyticsService { override fun logEvent(event: String) { Firebase.analytics.logEvent(event, null) } } // 测试模块 class TestAnalytics : AnalyticsService { val loggedEvents mutableListOfString() override fun logEvent(event: String) { loggedEvents.add(event) } } // 业务模块测试 Test fun purchase should log analytics event() { val testAnalytics TestAnalytics() val checkout CheckoutService(testAnalytics) checkout.processPurchase() assertTrue(testAnalytics.loggedEvents.contains(purchase_complete)) }10.2 动态功能模块测试对于动态交付的模块需要特殊测试策略RunWith(AndroidJUnit4::class) class DynamicFeatureTest { get:Rule val installRule DynamicInstallRule() Test fun dynamic feature should work() { val context ApplicationProvider.getApplicationContextContext() val intent Intent(context, DynamicActivity::class.java) installRule.installModule(dynamic_feature) val activityScenario ActivityScenario.launch(intent) activityScenario.onActivity { activity - assertEquals(Dynamic Content, activity.title) } } }11. 测试代码设计模式11.1 测试构建器模式替代冗长的对象创建class UserBuilder { private var id: Int 1 private var name: String test private var email: String? null fun withId(id: Int) apply { this.id id } fun withName(name: String) apply { this.name name } fun withEmail(email: String) apply { this.email email } fun build() User(id, name, email) } // 使用示例 val user UserBuilder() .withId(123) .withName(custom) .build()11.2 参数化测试使用JUnitParams减少重复测试代码RunWith(JUnitParamsRunner::class) class CalculatorParamTest { Test Parameters(method additionData) fun test addition(a: Int, b: Int, expected: Int) { assertEquals(expected, Calculator().add(a, b)) } private fun additionData() listOf( listOf(1, 1, 2), listOf(2, 3, 5), listOf(0, 0, 0), listOf(-1, 1, 0) ) }12. 测试资源管理12.1 测试资源文件在src/test/resources目录下放置测试数据test/resources/ └── testdata/ ├── user.json └── config.properties读取测试资源fun readTestResource(path: String): String { return javaClass.classLoader!! .getResourceAsStream(path)!! .bufferedReader() .use { it.readText() } } Test fun should parse user json() { val json readTestResource(testdata/user.json) val user Gson().fromJson(json, User::class.java) assertEquals(test, user.name) }12.2 Android Assets测试对于仪器化测试可以使用RunWith(AndroidJUnit4::class) class AssetTest { private val context InstrumentationRegistry.getInstrumentation().context Test fun should load test asset() { val input context.assets.open(test_config.json) val config Json.decodeFromStreamConfig(input) assertNotNull(config.apiUrl) } }13. 测试性能优化13.1 基准测试使用AndroidX Benchmark库测量性能RunWith(AndroidJUnit4::class) class DatabaseBenchmark { private lateinit var database: AppDatabase get:Rule val benchmarkRule BenchmarkRule() Before fun setup() { val context ApplicationProvider.getApplicationContextContext() database Room.inMemoryDatabaseBuilder(context, AppDatabase::class.java) .build() } Test fun insertUsers() benchmarkRule.measureRepeated { val users List(100) { User(id it, name user$it) } runWithTimingDisabled { database.clearAllTables() } database.userDao().insertAll(users) } }13.2 测试并行化配置Gradle并行测试android { testOptions { unitTests.all { maxParallelForks Runtime.runtime.availableProcessors().intdiv(2) ?: 1 forkEvery 100 } } }14. 测试安全实践14.1 敏感数据测试使用AndroidX Security库处理测试密钥RunWith(AndroidJUnit4::class) class EncryptionTest { private val masterKey MasterKey.Builder(ApplicationProvider.getApplicationContext()) .setKeyScheme(MasterKey.KeyScheme.AES256_GCM) .build() Test fun should encrypt and decrypt data() { val encryptedFile EncryptedFile.Builder( ApplicationProvider.getApplicationContext(), File(test_encrypted), masterKey, EncryptedFile.FileEncryptionScheme.AES256_GCM_HKDF_4KB ).build() encryptedFile.openFileOutput().use { it.write(secret.toByteArray()) } val decrypted encryptedFile.openFileInput().bufferedReader().readText() assertEquals(secret, decrypted) } }14.2 权限测试测试运行时权限处理RunWith(AndroidJUnit4::class) class PermissionTest { get:Rule val grantPermissionRule: GrantPermissionRule GrantPermissionRule.grant( Manifest.permission.ACCESS_FINE_LOCATION ) Test fun should access location when permission granted() { val locationManager ApplicationProvider.getApplicationContextContext() .getSystemService(Context.LOCATION_SERVICE) as LocationManager assertNotNull(locationManager.lastKnownLocation(LocationManager.GPS_PROVIDER)) } }15. 测试代码生成15.1 使用Square的JavaPoet生成测试创建测试类生成器fun generateTestClass(className: String, testMethods: ListString): JavaFile { val typeSpec TypeSpec.classBuilder(${className}Test) .addModifiers(Modifier.PUBLIC) .addMethods(testMethods.map { methodName - MethodSpec.methodBuilder(methodName) .addAnnotation(Test::class.java) .addModifiers(Modifier.PUBLIC) .addStatement(// TODO: implement test) .build() }) .build() return JavaFile.builder(com.example, typeSpec) .build() } // 使用示例 generateTestClass(UserRepository, listOf( shouldSaveUser, shouldLoadUserById, shouldDeleteUser )).writeTo(System.out)15.2 使用KotlinPoet生成DSL测试创建更友好的测试DSLfun createBehaviorTest(className: String): FileSpec { return FileSpec.builder(com.example, ${className}BehaviorTest) .addType(TypeSpec.classBuilder(${className}BehaviorTest) .addFunction(FunSpec.builder($className should behave correctly) .addAnnotation(Test::class.java) .addCode( val subject $className() // Given ${$}N // When ${$}N // Then ${$}N .trimIndent()) .build()) .build()) .build() }16. 遗留代码测试策略16.1 测试已有代码对于未设计可测试性的代码可采用以下策略提取接口将具体实现替换为接口依赖注入通过构造函数或setter注入依赖包装静态方法用实例方法包装静态调用测试子类创建可重写的测试子类// 原始代码 class LegacyService { fun process(data: String): String { // 直接调用静态方法 val result LegacyUtil.transform(data) Database.save(result) return result } } // 重构后 class LegacyService( private val transformer: DataTransformer LegacyTransformer(), private val repository: DataRepository DatabaseRepository() ) { fun process(data: String): String { val result transformer.transform(data) repository.save(result) return result } } // 测试 Test fun legacy service should process data() { val mockTransformer mockDataTransformer() when(mockTransformer.transform(any())).thenReturn(test) val service LegacyService(mockTransformer, FakeRepository()) assertEquals(test, service.process(input)) }16.2 特征测试当无法全面测试时针对关键特征编写测试Test fun legacy code critical feature() { // 直接调用遗留方法 val result LegacyClass.doCrucialCalculation(input) // 验证关键特征而非具体实现 assertTrue(result.contains(expected)) assertTrue(result.length in 5..20) }17. 测试文档化17.1 活文档生成使用Spek或Cucumber创建可执行规范RunWith(JUnitPlatform::class) class LoginSpec : Spek({ describe(Login feature) { val loginService by memoized { mockLoginService() } val validator by memoized { LoginValidator() } context(with valid credentials) { beforeEach { when(loginService.login(user, pass)).thenReturn(true) } it(should return success) { assertTrue(validator.validate(user, pass, loginService)) } } } })17.2 测试用例文档使用Dokka生成测试文档/** * 测试用户登录功能 * * 场景 * - 有效凭证应登录成功 * - 无效凭证应拒绝登录 * - 空用户名应抛出异常 */ class LoginTest { Test fun valid credentials() { ... } Test fun invalid credentials() { ... } Test(expected IllegalArgumentException::class) fun empty username() { ... } }18. 测试文化构建18.1 团队测试准则制定团队测试规范提交前必须通过所有单元测试代码审查检查测试覆盖率构建失败优先修复失败的测试测试代码与生产代码同等质量标准18.2 测试知识分享定期组织测试技巧分享会测试代码审查测试挑战赛如最难测的代码测试重构工作坊19. 测试框架扩展19.1 自定义断言创建领域特定断言fun User.assertValid() { assertTrue(id 0, User ID should be positive) assertNotNull(name, User name should not be null) assertTrue(email?.contains() true, Invalid email format) } // 使用示例 Test fun created user should be valid() { val user repository.createUser(test) user.assertValid() }19.2 自定义测试规则创建JUnit规则处理重复逻辑class DatabaseRule : TestWatcher() { lateinit var database: AppDatabase override fun starting(description: Description) { val context ApplicationProvider.getApplicationContextContext() database Room.inMemoryDatabaseBuilder(context, AppDatabase::class.java) .allowMainThreadQueries() .build() } override fun finished(description: Description) { database.close() } } // 使用示例 RunWith(AndroidJUnit4::class) class DaoTest { get:Rule val dbRule DatabaseRule() Test fun test query() { val dao dbRule.database.userDao() // 测试代码 } }20. 测试未来趋势20.1 快照测试使用Shot验证UI一致性RunWith(AndroidJUnit4::class) class UiSnapshotTest { get:Rule val rule ActivityScenarioRule(MainActivity::class.java) Test fun verifyMainScreen() { rule.scenario.onActivity { activity - compareScreenshot(activity, main_screen) } } }20.2 AI辅助测试探索AI测试生成工具Diffblue Cover自动生成单元测试Applitools视觉AI测试Testim自修复UI测试实际项目中我通常会结合传统测试方法和AI工具在关键路径上仍保持手动编写测试而在边缘用例和回归测试中引入AI辅助。