android-tdd

Apply TDD to Android ViewModels and Repositories by selecting the unit test tier and writing failing tests that drive the implementation using coroutine testing patterns with runTest. This approach guides you to implement code through the Android TDD cycle before refactoring to pass the test.

The best way to test Compose UI components in an Android TDD workflow is using instrumented testing with specific Compose UI testing rules. This ensures your UI components meet the required behavior by driving the implementation through failing UI tests before writing the actual Compose code.

You should use fake implementations over mocks when writing Android Kotlin tests. This fake-first strategy provides more reliable and maintainable tests by utilizing real implementations of your interfaces rather than relying on mock frameworks that can tightly couple tests to implementation details.

Yes, this Android testing approach explicitly supports Hilt testing patterns. It integrates Hilt dependency injection into the three-tier testing model, allowing you to write and execute tests for ViewModels, Repositories, and DAOs that rely on Hilt-provided dependencies.

Choose between unit, integration, and instrumented testing by selecting the lowest viable test tier for your specific Android or KMP module. This three-tier testing model ensures you start with the fastest, most isolated tests possible before moving to higher-level integration or instrumented tests.

Yes, you can use Roborazzi for screenshot testing within an Android TDD cycle. The testing guidance includes Roborazzi-based screenshot testing patterns to capture and verify UI rendering, ensuring your visual implementation matches expected outcomes after driving the code through test failures.