Follow-up to lane 5 (#250, PR #274), which covered the 5 highest-value untested Compose screens (Outbox, Drafts, ProblemReports, AccountPicker, Signatures). These still lack a dedicated UI test — mostly OAuth/permission-launcher-heavy or trivial static screens:
AppPasswordSetupScreen
AddAnotherAccountScreen
LockScreen
SignatureEditScreen
ReportReviewScreen
compose/formatColorSwatch / ColorSwatchRow
Add UI/E2E tests for these (or justify exclusion for the launcher-heavy onboarding screens that need intent/permission stubbing). Needed so lane 6's coverage ratchet (#251, enforce >=95%) can pass on the ui package.
Follow-up to lane 5 (#250, PR #274), which covered the 5 highest-value untested Compose screens (Outbox, Drafts, ProblemReports, AccountPicker, Signatures). These still lack a dedicated UI test — mostly OAuth/permission-launcher-heavy or trivial static screens:
- `AppPasswordSetupScreen`
- `AddAnotherAccountScreen`
- `LockScreen`
- `SignatureEditScreen`
- `ReportReviewScreen`
- `compose/format` `ColorSwatch` / `ColorSwatchRow`
Add UI/E2E tests for these (or justify exclusion for the launcher-heavy onboarding screens that need intent/permission stubbing). Needed so **lane 6's coverage ratchet (#251, enforce >=95%)** can pass on the `ui` package.
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.
Follow-up to lane 5 (#250, PR #274), which covered the 5 highest-value untested Compose screens (Outbox, Drafts, ProblemReports, AccountPicker, Signatures). These still lack a dedicated UI test — mostly OAuth/permission-launcher-heavy or trivial static screens:
AppPasswordSetupScreenAddAnotherAccountScreenLockScreenSignatureEditScreenReportReviewScreencompose/formatColorSwatch/ColorSwatchRowAdd UI/E2E tests for these (or justify exclusion for the launcher-heavy onboarding screens that need intent/permission stubbing). Needed so lane 6's coverage ratchet (#251, enforce >=95%) can pass on the
uipackage.