Conversation
DAOs, entities, and database class are now excluded from coverage. Migrations remain visible at 0% with documentation explaining they're tested via instrumented tests.
Exclude Android UI packages from coverage reports to show accurate metrics for testable business logic.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR completes the unit test coverage improvements across all modules, achieving production-ready quality with 90.7% line and 76.4% branch coverage. All remaining gaps are infrastructure code (Kotlin stdlib, coroutines, framework wrappers).
Changes
Tests Added (9 new tests)
UpdateUsersLastSessionTimestampUseCase- 8 comprehensive tests covering empty input, success, partial failure, error pathsInsertSessionUseCase- 1 test for timestamp update failure scenarioCode Changes
SoundPoolFactoryImplfrom coverage (framework wrapper with zero business logic)Documentation
Coverage Impact
Session Domain
Session Shared-UI
Overall Project
Testing Philosophy
✅ What we test: Business logic, error handling, edge cases, data transformations
❌ What we don't test: Kotlin stdlib (Flow, comparators), coroutines (withContext), Android frameworks (Room, Compose)
Result: Coverage metrics represent genuine protection of business logic, not inflated numbers from testing framework code.