Strangler lane 5 of 6 (coverage → >95%; see lane 1). Depends on #192 / PR #241.
Scope:ui/** Compose screens & components (the view layer that lane 4's ViewModel unit tests can't reach).
Test approach:instrumented Compose UI / E2E flows across the Gradle Managed Device matrix (e2eGroupDebugAndroidTest). Keep the managed-device list in app/build.gradle.kts in lockstep with the E2E matrix in .github/workflows/ci.yml. Follow existing E2E conventions (e.g. append new toolbar controls at the END so performClick targets stay stable). Cover the primary journeys per screen: onboarding/login, mailbox list + paging, message view, compose/send, settings, problem-reports.
Target: exercise the UI layer end-to-end so view code reaches ≥95% combined with lane 4; then ratchet the floor.
**Strangler lane 5 of 6** (coverage → >95%; see lane 1). Depends on #192 / PR #241.
**Scope:** `ui/**` Compose screens & components (the view layer that lane 4's ViewModel unit tests can't reach).
**Test approach:** **instrumented Compose UI / E2E** flows across the Gradle Managed Device matrix (`e2eGroupDebugAndroidTest`). Keep the managed-device list in `app/build.gradle.kts` in lockstep with the E2E matrix in `.github/workflows/ci.yml`. Follow existing E2E conventions (e.g. append new toolbar controls at the END so `performClick` targets stay stable). Cover the primary journeys per screen: onboarding/login, mailbox list + paging, message view, compose/send, settings, problem-reports.
**Target:** exercise the UI layer end-to-end so view code reaches ≥95% combined with lane 4; then ratchet the floor.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Strangler lane 5 of 6 (coverage → >95%; see lane 1). Depends on #192 / PR #241.
Scope:
ui/**Compose screens & components (the view layer that lane 4's ViewModel unit tests can't reach).Test approach: instrumented Compose UI / E2E flows across the Gradle Managed Device matrix (
e2eGroupDebugAndroidTest). Keep the managed-device list inapp/build.gradle.ktsin lockstep with the E2E matrix in.github/workflows/ci.yml. Follow existing E2E conventions (e.g. append new toolbar controls at the END soperformClicktargets stay stable). Cover the primary journeys per screen: onboarding/login, mailbox list + paging, message view, compose/send, settings, problem-reports.Target: exercise the UI layer end-to-end so view code reaches ≥95% combined with lane 4; then ratchet the floor.