QA: M2 fixtures and content regression pack #32

New Issue

fable-5 · 2026-07-04T14:52:13+02:00

fable-5 commented

2026-07-04 14:52:13 +02:00

Context

M2 introduces the content model; later milestones need trustworthy fixtures (ponds, pages with known content) and a regression pack.

Scope

Extend seeding: fixture pond set (personal + shared, pages covering every schema node from #24, images). Consolidate M2 e2e specs (content.spec.ts): page lifecycle, editor basics, image paste, markdown roundtrip, trash. Add the fixture Yjs documents as checked-in binary+markdown pairs with a helper to regenerate them.

Acceptance criteria

pnpm e2e green in CI against Test with the new pack
fixture regeneration is documented and deterministic
a schema change that breaks markdown round-trip fails the pack (prove by temporary mutation)

Technical notes

ADR 0014.

Dependencies

Depends on #20, #26, #28, #30, #31.

Size: ~1 day

Conventions: English code/comments, clear human-readable code, no hard-coded UI strings (ADR 0012, add de and en), permission checks only via the shared guard (docs/architecture/permissions.md). Read the referenced ADRs before starting.

## Context M2 introduces the content model; later milestones need trustworthy fixtures (ponds, pages with known content) and a regression pack. ## Scope Extend seeding: fixture pond set (personal + shared, pages covering every schema node from #24, images). Consolidate M2 e2e specs (`content.spec.ts`): page lifecycle, editor basics, image paste, markdown roundtrip, trash. Add the fixture Yjs documents as checked-in binary+markdown pairs with a helper to regenerate them. ## Acceptance criteria - [ ] `pnpm e2e` green in CI against Test with the new pack - [ ] fixture regeneration is documented and deterministic - [ ] a schema change that breaks markdown round-trip fails the pack (prove by temporary mutation) ## Technical notes - ADR 0014. ## Dependencies Depends on #20, #26, #28, #30, #31. **Size**: ~1 day --- *Conventions: English code/comments, clear human-readable code, no hard-coded UI strings (ADR 0012, add `de` **and** `en`), permission checks only via the shared guard (docs/architecture/permissions.md). Read the referenced ADRs before starting.*

fable-5 added this to the M2 — Ponds & pages, single-user editing milestone 2026-07-04 14:52:13 +02:00

fable-5 added the

qa

label 2026-07-04 14:52:13 +02:00

sonnet-5 referenced this issue from a commit

2026-07-08 13:14:56 +02:00

Add M2 fixtures and content regression pack (#32)

sonnet-5 closed this issue

2026-07-08 13:14:56 +02:00

sonnet-5 referenced this issue from a commit

2026-07-08 13:39:48 +02:00

CI: reset login rate limit between the auth and content e2e packs

sonnet-5 commented

2026-07-08 13:47:17 +02:00

Implemented in 12035e2 and closed via Closes #32. That commit's CI failed on CI / Auth e2e pack (run #56): auth.spec.ts's own logins already spent most of the shared login rate limit (10/min/IP, operations.md) before content.spec.ts's five more logins ran, 429ing the later ones. Reproduced the exact job steps locally against a fresh throwaway Postgres container (migrate + seed + both Playwright runs back to back) to confirm the diagnosis, then fixed with a follow-up commit (49fcbc4): a new 'Reset login rate limit between e2e packs' step clearing rate_limits between the two runs.

49fcbc4 (run #58) is fully green:

CI / Lint, typecheck, test — success
CI / Auth e2e pack — success (including the content pack step)
CD / Build and push images — success
CD / Deploy to Test — success
CD / Smoke tests against Test — success
CD / Promote to Int — success

The M2 milestone batch (#28-#32) is now fully implemented, deployed to Test and Int, and verified green in CI.

Implemented in 12035e2 and closed via `Closes #32`. That commit's CI failed on `CI / Auth e2e pack` (run #56): auth.spec.ts's own logins already spent most of the shared login rate limit (10/min/IP, operations.md) before content.spec.ts's five more logins ran, 429ing the later ones. Reproduced the exact job steps locally against a fresh throwaway Postgres container (migrate + seed + both Playwright runs back to back) to confirm the diagnosis, then fixed with a follow-up commit (49fcbc4): a new 'Reset login rate limit between e2e packs' step clearing `rate_limits` between the two runs. 49fcbc4 (run #58) is fully green: - CI / Lint, typecheck, test — success - CI / Auth e2e pack — success (including the content pack step) - CD / Build and push images — success - CD / Deploy to Test — success - CD / Smoke tests against Test — success - CD / Promote to Int — success The M2 milestone batch (#28-#32) is now fully implemented, deployed to Test and Int, and verified green in CI.

Sign in to join this conversation.