meshtastic/Meshtastic-Android
1
0
Fork 0
mirror of https://github.com/meshtastic/Meshtastic-Android.git synced 2026-04-20 22:23:37 +00:00
Code Issues Projects Releases Packages Wiki Activity

chore(conductor): Mark track 'Migrate tests to KMP best practices and expand coverage' as complete

Browse source
This commit is contained in:
James Rich 2026-03-18 16:46:10 -05:00
parent 0e1461b5e4
commit 2395cb91e1
33 changed files with 358 additions and 307 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/decisions/testing-consolidation-2026-03.md
View file

@ -31,7 +31,7 @@ Created `core:testing` as a lightweight, reusable module for **shared test doubl
```
core:testing
├── depends on: core:model, core:repository
├── depends on: kotlin("test"), mockk, kotlinx.coroutines.test, turbine, junit
├── depends on: kotlin("test"), kotlinx.coroutines.test, turbine, junit
└── does NOT depend on: core:database, core:data, core:domain
```

6
docs/decisions/testing-in-kmp-migration-context.md
View file

@ -36,9 +36,9 @@ KMP Migration Timeline
### Before KMP Testing Consolidation
```
Each module had scattered test dependencies:
feature:messaging → libs.junit, libs.mockk, libs.turbine
feature:node → libs.junit, libs.mockk, libs.turbine
core:domain → libs.junit, libs.mockk, libs.turbine
feature:messaging → libs.junit, libs.turbine
feature:node → libs.junit, libs.turbine
core:domain → libs.junit, libs.turbine
↓
Result: Duplication, inconsistency, hard to maintain
Problem: New developers don't know testing patterns