docs(docs): V1-1.5 counts after the gate fixes, what the gates found
This commit is contained in:
1 parent
567ad40c80
commit
d8e86a4229
2 files changed
+7
-3
No files matched your search
@@ -36,8 +36,8 @@ caught (`V1-1_OWNERS_ANIMALS.md` §8.3). The axe exceptions match rule,
|
||||
selector, markup and route.
|
||||
V1-1.5 (2026-10-26): supabase vitest 92 (access layer 33); sandbox suites 54
|
||||
(`clients-access.sandbox.ts` 8: the access layer through supabase-js against
|
||||
real GoTrue and PostgREST); app vitest 508 (client screens 22, form schema 20,
|
||||
workspace and account change 6); `e2e:shell` 42 (client journeys 36, FR/EN,
|
||||
real GoTrue and PostgREST); app vitest 509 (client screens 22, form schema 20,
|
||||
workspace and account change 7); `e2e:shell` 42 (client journeys 36, FR/EN,
|
||||
desktop and 375 px, axe). The shell suite keeps no HTML report.
|
||||
|
||||
## 1. Layers
|
||||
|
||||
@@ -1292,13 +1292,17 @@ already carried an `h1` with the page title on large screens before V1-1.5;
|
||||
the client pages add their own `h1` in `main`, as the existing pages do.
|
||||
|
||||
Tests: supabase vitest 92 (access layer 33), sandbox suites 54 (access layer
|
||||
8); app vitest 508 (client screens 22, form schema 20, store 15); Chromium
|
||||
8); app vitest 509 (client screens 22, form schema 20, store 16); Chromium
|
||||
`e2e:shell` 42 (client journeys 36: create, search, edit, archive, archived
|
||||
filter, restore, pages, keyboard only, two accounts, concurrent edit, retry
|
||||
after a lost answer, network failures, leave guard, change of language; FR
|
||||
and EN, desktop and 375 px, axe on every state with no exception of RR-7
|
||||
inherited). Report check: the shell suite's HTML report kept the typed
|
||||
passwords of its throwaway accounts; it was removed (`BROWSER_TESTS.md` §3).
|
||||
Gates also found: a re-read of the same account (`USER_UPDATED`) set the
|
||||
workspace back to loading and unmounted an open form (fixed: a ready workspace
|
||||
stays on screen until the answer); the « introuvable » screen did not focus its
|
||||
heading (fixed).
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in new issue
Block a user