Test expectations for beta #49

New issue

Closed

opened 2026-08-03 22:43:00 +00:00 by TheAnachronism · 1 comment

TheAnachronism commented

2026-08-03 22:43:00 +00:00

Owner

Part of #41
Blocked by: #48

Question

What automated-test bar does an established codebase require for 1.0 beta — kinds of coverage that must exist, acceptable gaps, and whether current tests already meet that bar?

Part of #41 Blocked by: #48 ## Question What automated-test bar does an established codebase require for 1.0 beta — kinds of coverage that must exist, acceptable gaps, and whether current tests already meet that bar?

TheAnachronism added the

wayfinder:grilling

label

2026-08-03 22:43:01 +00:00

TheAnachronism referenced this issue

2026-08-04 00:48:05 +00:00

CI quality gates for beta #47

TheAnachronism self-assigned this

2026-08-04 18:30:19 +00:00

TheAnachronism commented

2026-08-04 18:36:55 +00:00

Author

Owner

Resolution

Automated-test bar for sideload-to-friends 1.0 beta (criteria only — implement later):

Must

Green suite: flutter test passes on the beta-cut commit (already required by CI quality gates for beta).
Blocker regression tests: each beta Blocker fix from Beta-blocking known issues (Fresh −3 unread delta; List/Drawer sid re-login) ships with a regression test at the best seam — prefer unit/controller like the existing suite. Widget/integration not required for this must.

Document as debt (not blockers)

Test landscape snapshot gaps stay acceptable for beta readiness, named in the eng bar as debt: Sign-in / Settings / Manage-accounts widgets, ReaderVideo / embed cards, url_launcher, ThemeMode.dark smoke, PrefsAccountStore wiring, integration happy path.

Not must for beta

Net-new coverage kinds (broad widget suite, integration_test/, device/emulator)
Regression-test musts for Document / Ignore known-issue fixes

Why

Friends beta needs a green regression floor plus protection when the two product Blockers are fixed — not a UI/E2E maturity campaign. Current domain/API/controller strength already meets the “established enough” bar once Blockers are covered.

Does current suite meet the bar?

Yes, for kinds of coverage — once the two Blocker fixes land with their regression tests and the suite stays green. Until those Blocker tests exist, the bar is not yet satisfied for readiness sign-off.

## Resolution **Automated-test bar** for sideload-to-friends **1.0 beta** (criteria only — implement later): ### Must 1. **Green suite:** `flutter test` passes on the beta-cut commit (already required by [CI quality gates for beta](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/47)). 2. **Blocker regression tests:** each beta **Blocker** fix from [Beta-blocking known issues](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/45) (Fresh −3 unread delta; List/Drawer sid re-login) ships with a regression test at the best seam — prefer unit/controller like the existing suite. Widget/integration not required for this must. ### Document as debt (not blockers) [Test landscape snapshot](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/48) gaps stay acceptable for beta readiness, named in the eng bar as debt: Sign-in / Settings / Manage-accounts widgets, ReaderVideo / embed cards, `url_launcher`, `ThemeMode.dark` smoke, PrefsAccountStore wiring, integration happy path. ### Not must for beta - Net-new coverage *kinds* (broad widget suite, `integration_test/`, device/emulator) - Regression-test musts for Document / Ignore known-issue fixes ### Why Friends beta needs a green regression floor plus protection when the two product Blockers are fixed — not a UI/E2E maturity campaign. Current domain/API/controller strength already meets the “established enough” bar once Blockers are covered. ### Does current suite meet the bar? **Yes, for kinds of coverage** — once the two Blocker fixes land *with* their regression tests and the suite stays green. Until those Blocker tests exist, the bar is not yet satisfied for readiness sign-off.

TheAnachronism closed this issue

2026-08-04 18:36:55 +00:00

TheAnachronism referenced this issue

2026-08-04 18:37:23 +00:00

1.0 beta release readiness #41