docs(supabase): DEV acceptance run, RESP-01 and AVATAR-01 recorded
This commit is contained in:
1 parent
a70166ea11
commit
8c8478c052
4 files changed
+31
-2
No files matched your search
@@ -8,7 +8,7 @@ Chromium only until V1-5. The suites live in `apps/app/e2e`.
|
||||
| Command | Backend | Dev server | Content |
|
||||
|---|---|---|---|
|
||||
| `pnpm e2e:ui` | none | Vite on `127.0.0.1:5191` | `e2e/ui/dialog.spec.ts`: the D13 contract of the shared Dialog on a test page; `e2e/ui/local-tool.spec.ts`: the disclaimer, edit and replace dialogs on the real local-tool routes |
|
||||
| `pnpm e2e:shell` | the isolated stack of `pnpm db:sandbox` | Vite on `127.0.0.1:5192` | `e2e/shell/shell.spec.ts`: sign-in, dashboard, the account photo confirmation, the phone drawer; `e2e/shell/clients.spec.ts`: the client journeys (V1-1.5); `e2e/shell/animals.spec.ts`: the animal and relation journeys (V1-1.6, contract §11.8) |
|
||||
| `pnpm e2e:shell` | the isolated stack of `pnpm db:sandbox` | Vite on `127.0.0.1:5192` | `e2e/shell/shell.spec.ts`: sign-in, dashboard, the account photo confirmation, the phone drawer; `e2e/shell/clients.spec.ts`: the client journeys (V1-1.5); `e2e/shell/animals.spec.ts`: the animal and relation journeys (V1-1.6, contract §11.8); `e2e/shell/responsive.spec.ts`: no sideways scroll on nine shell pages, the archive confirmations and the drawer at 320, 360, 375, 390 and 430 px (phone project) and 1280 px, long values, the dashboard e-mail shown whole (RESP-01) |
|
||||
|
||||
Each suite runs on two Chromium projects: `chromium-desktop` (1280 × 800) and
|
||||
`chromium-375` (375 × 667, mobile viewport, touch). A test tagged `@phone`
|
||||
|
||||
@@ -260,7 +260,15 @@ token, no user content.
|
||||
4. Poll the own row every 1 s, 30 s at most: `clean` → download
|
||||
`object_key` (`storage.from('avatars').download`), keep a blob URL in the
|
||||
auth store; `rejected` → message per code; still `uploaded` after 30 s →
|
||||
"processing, come back later" (the next mount polls again).
|
||||
"processing, come back later" (the next mount polls again). Only a row
|
||||
the section knows at mount resumes: after a full page reload the section
|
||||
mounts before the auth store has read the rows, so it shows the clean
|
||||
photo with « Modifier » and « Supprimer » enabled, and a new save
|
||||
supersedes the waiting row (`deleted`, keys enqueued). An in-app return to
|
||||
Mon compte resumes the polling. Without a running worker (a DEV stack where
|
||||
`docker compose --profile worker up worker` was not started, §3.2 of
|
||||
SUPABASE.md) every new photo stays `uploaded` and ends on that message;
|
||||
the clean photo is kept (AVATAR-01, 2026-10-27, isolated reproduction).
|
||||
5. "Supprimer la photo": confirmation dialog → `remove_avatar()` → monogram.
|
||||
|
||||
Closed failure kinds the UI phrases (`AssetFailure.kind`): `too_large`,
|
||||
|
||||
@@ -711,6 +711,23 @@ means a sign-up on DEV, the owner's choice); the back and forward guard
|
||||
(accepted debt). This acceptance is no production security certification:
|
||||
RR-1 to RR-10 stay open.
|
||||
|
||||
Run of 2026-10-27 (the owner's results; the detailed records stay outside
|
||||
Git): the 19 lines validated in French one by one; English validated as a
|
||||
whole, four lines at 375 px recorded one by one; isolation A, B and owner
|
||||
checked. Two anomalies:
|
||||
|
||||
- RESP-01, sideways scroll at 375 px: the global scroll first seen came from
|
||||
the browser zoom (the owner's measures without zoom: `/app` and
|
||||
`/app/clients` at 375 and 320 px, no overflow; no other page is declared
|
||||
conform by them). A real defect found apart, on the isolated stack: an
|
||||
account e-mail longer than the card (from about 31 characters at 320 px)
|
||||
widened the dashboard cards past a phone screen (implicit grid track); fixed, covered by
|
||||
`e2e/shell/responsive.spec.ts`; the owner's check of the fix is pending.
|
||||
- AVATAR-01, a new photo ends on « Le traitement prend plus de temps que
|
||||
prévu »: expected on DEV without a running worker (STORAGE.md §4 step 4);
|
||||
the pipeline completes once a worker runs (reproduced on the isolated
|
||||
stack, never on DEV). Open until the owner decides how DEV runs the worker.
|
||||
|
||||
## 4. Writing a migration
|
||||
|
||||
1. `pnpm supabase migration new <name>` creates `supabase/migrations/<timestamp>_<name>.sql`.
|
||||
|
||||
Reference in new issue
Block a user