T-VEK2-backup-checklist-e2e-suite

State: planning/proposed · Impact: high · Complexity: medium

Goal

Turn the manual Determined Backup checklist into a Playwright suite that runs on the web build against the real backend, in a scratch root, so a backup regression is caught without a person clicking through the app.

Today

Location	Role today
solutions/determined/tests/ui/backup/backup.e2e.ts	One end-to-end test, launched by serve-backup.ts
solutions/determined/tests/ui/serve-backup.ts	A serveScratchApp(scratchPlatform(...)) launcher on e2e-backup (15109). The checklist cases are not written yet
solutions/determined/tests/ui/backup/harness.ts	The spec’s scratch fixture, from @sksizer/app-harness/playwright
solutions/determined/moon.yml	test-ui-backup task exists, runInCI: false
solutions/determined/tests/fixtures/obsidian-vault	Fixture vault

Proposed

The backup project runs through scratchPlatform and covers the checklist:

Case	Asserts
First-run gate	Vault chosen via the typed path field on web
Back up	A snapshot appears
Restore and Undo	File content returns, then Undo reverts it
Deleted-file restore	A deleted file comes back
Store path, Finder hidden on web	The store path shows; the Finder reveal button is absent on web
Schedule	A 1-minute schedule produces a snapshot; tagged slow
Restart persistence	After restart(), settings and snapshots remain

serve-backup.ts is deleted.

Approach

1. Pass schedule to scratchPlatform for the schedule case.
2. Add the missing cases to the existing spec.
3. Tag the schedule case slow so default runs skip it.
4. Delete serve-backup.ts, so no serve-*.ts launcher remains for backup, in the same shape T-GXNH uses for the other suites.

Areas

Area	Note
solutions/determined/tests/ui/backup/	Suite
solutions/determined/playwright.config.ts	Backup project
solutions/determined/tests/ui/serve-backup.ts	Deleted

Acceptance criteria

• AC-1: moon run determined-root:test-ui-backup passes three runs in a row locally.
• AC-2: The harness’s post-boot isolation check passes on every run. With a marker file touched before the run, find <real suite durable home> -newer <marker> lists nothing after it. Note: backup state stayed in the scratch root on every run; the listed writes came from concurrent polish e2e (serve-polish-lint.ts) and the installed Fitness app, so a clean back-to-back run needs those quiet.
• AC-3: Every case in the table above has a test; the schedule case runs only when slow tests are enabled.
• AC-4: serve-backup.ts no longer exists.

Out of scope

• CI wiring (T-CAWD).
• Other platform-server suites (T-GXNH).

Dependencies

• T-BDRY for --backup-schedule.
• T-4HBC for the harness and adapter.

Discovery context

• Manual testing of Determined Backup.app showed most of the checklist can run on the web build.

Depends on

T-BDRY, T-4HBC

---

← Back to Tasks