EPIC B: CI + Test Reliability (Week 1-2) — Phase 3: Scope #39

New issue

Closed

opened 2026-05-28 01:03:05 +00:00 by Mark · 1 comment

Mark commented

2026-05-28 01:03:05 +00:00

Owner

Phase 3: Scope

CI checks for lint, typecheck, build
Deterministic test data and environment setup
Critical path Playwright coverage

Decomposed from nodedesk#2

## Phase 3: Scope - CI checks for lint, typecheck, build - Deterministic test data and environment setup - Critical path Playwright coverage --- _Decomposed from [nodedesk#2](https://forgejo.tail018ac4.ts.net/Mark/nodedesk/issues/2)_

Mark added the

needs-triage

label

2026-05-28 01:03:05 +00:00

Mark referenced this issue

2026-05-28 01:03:08 +00:00

EPIC B: CI + Test Reliability (Week 1-2) #2

Mark added

blocked:needs-decision

and removed

needs-triage

labels

2026-05-28 01:08:12 +00:00

Mark commented

2026-05-28 01:08:12 +00:00

Author

Owner

⏸ Needs Decision

Blocking factors:

Didn't meet auto-approve criteria — scope=medium, risk=low, spec=aligned

Scope: medium Risk: low Spec: aligned Type: chore
Summary: Set up CI pipeline (lint, typecheck, build), harden deterministic test environment, and write critical-path Playwright E2E tests.
Suggestion: Create a Forgejo Actions workflow (repo is on a Forgejo instance) that runs lint/typecheck/build, leverages the existing global-setup.ts infrastructure for DB seeding, and adds ~5-8 Playwright spec files covering auth flow (login/logout/signup), client CRUD, system CRUD, and dashboard as critical paths. The Docker Compose stack already defines all infra services (db, minio) needed for CI.
Rationale: Scope is medium: zero existing test spec files and no CI config means ~5-15 new files (CI workflow + Playwright specs + possibly a CI env file). Risk is low because this is entirely additive infrastructure and testing — no production code paths are modified. Spec is aligned: Playwright is already a dependency, test:e2e script exists, Docker Compose defines the full stack, and the seed script + global-setup already handle deterministic data. This is a chore (infrastructure/tooling setup) rather than a product feature.

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=low, spec=aligned --- **Scope:** medium **Risk:** low **Spec:** aligned **Type:** chore **Summary:** Set up CI pipeline (lint, typecheck, build), harden deterministic test environment, and write critical-path Playwright E2E tests. **Suggestion:** Create a Forgejo Actions workflow (repo is on a Forgejo instance) that runs lint/typecheck/build, leverages the existing global-setup.ts infrastructure for DB seeding, and adds ~5-8 Playwright spec files covering auth flow (login/logout/signup), client CRUD, system CRUD, and dashboard as critical paths. The Docker Compose stack already defines all infra services (db, minio) needed for CI. **Rationale:** Scope is medium: zero existing test spec files and no CI config means ~5-15 new files (CI workflow + Playwright specs + possibly a CI env file). Risk is low because this is entirely additive infrastructure and testing — no production code paths are modified. Spec is aligned: Playwright is already a dependency, test:e2e script exists, Docker Compose defines the full stack, and the seed script + global-setup already handle deterministic data. This is a chore (infrastructure/tooling setup) rather than a product feature. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.

Mark added

triage-approved

quickfix

and removed

blocked:needs-decision

labels

2026-05-28 07:18:33 +00:00

Mark referenced this issue from a commit

2026-05-28 09:13:48 +00:00

feat(ci): Phase 3 - CI checks, deterministic test fixtures, critical path Playwright coverage

Mark

2026-05-28 09:13:48 +00:00