Visual E2E at five viewports, typecheck e2e-tests in the gate, drop unused icons
CI / full-gate (push) Successful in 3m29s
CI / full-gate (push) Successful in 3m29s
This commit is contained in:
@@ -1502,7 +1502,7 @@ no Node/browsers on the host. Five suites, each on its own stack:
|
||||
|
||||
| Suite | Compose overlay | Covers |
|
||||
| --- | --- | --- |
|
||||
| `visual.spec.ts` + `language.spec.ts` | `e2e-tests/compose.visual.yml` | Ory-free: the rendered design system (app shell, theme switch, mobile off-canvas, icon sprite, CSRF-guarded sign-out, landing, 404), plugin permission-gating, and [language switching](#languages-i18n) |
|
||||
| `visual.spec.ts` + `language.spec.ts` | `e2e-tests/compose.visual.yml` | Ory-free: the rendered design system (app shell at five widths from 1920px to 320px, theme switch, mobile off-canvas, icon sprite, CSRF-guarded sign-out, landing, 404), plugin permission-gating, and [language switching](#languages-i18n) |
|
||||
| `auth-refresh.spec.ts` | `e2e-tests/compose.auth.yml` | The real Ory stack with the session→JWT TTL cut to 8s: a lapsed JWT is silently re-minted from the live Kratos session, and once revoked the stale cookie is cleared |
|
||||
| `oauth-login.spec.ts` | `e2e-tests/compose.oauth.yml` | Another app logging in through us — register a client, start an authorization flow, `/oauth2/login` accept, `/oauth2/consent` Allow → authorization code |
|
||||
| `full-flow.spec.ts` | `e2e-tests/compose.full.yml` | The browser UI: password + mocked-SSO login, menu filtering by permission, admin users/groups/permissions CRUD, OAuth2-clients register → one-time secret → delete, a gated plugin page, logout |
|
||||
@@ -1531,7 +1531,7 @@ Ory-backed ones share one backend and stay on Chromium.
|
||||
|
||||
### The full gate (one command)
|
||||
|
||||
`ci.sh` is the whole gate in one reproducible command — typecheck → unit tests →
|
||||
`ci.sh` is the whole gate in one reproducible command — typecheck (the specs in `e2e-tests/` too) → unit tests →
|
||||
each E2E suite against its own fresh stack, with a guaranteed `down -v` after each (even on
|
||||
failure) and a non-zero exit on the first failure. Run it locally before a release, or wire
|
||||
it into your CI service:
|
||||
|
||||
Reference in New Issue
Block a user