Menu
Maintain E2E spec order for full reports and respect parameter order for specified runs.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
When changing API routes, auth, or env-dependent behavior, add or update the corresponding integration tests and keep the test file layout consistent.
When adding or changing files under infra/k8s/ or sync targets for k8s, know what Argo CD syncs and remind the user to push to Git so the cluster can sync.
Keeps tools/generate-data seeders and docs in sync when main or management DB schema or ORM entities change. Use when adding or changing tables/entities in packages/orm, packages/management-orm, or infra database migrations.
When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code.
Use when adding or changing environment variables, infra/env/classification YAML, scripts/env-classification, K8s env render, or local env generation.
Common patterns for the Boilerplate HTTP API (Express)
| name | e2e-report-order |
| description | Maintain E2E spec order for full reports and respect parameter order for specified runs. |
| version | 1.0.0 |
Use this skill when working with E2E report ordering: full-suite reports (make e2e_test_report) or scoped runs with SPEC / WEB_SPEC / MGMT_SPEC.
The full E2E report (make e2e_test_report) produces four HTML reports (four browser tabs when opened):
AUTH_MODE=admin_only_username; report dir web/.AUTH_MODE=user_signup_email, Mailpit; report dir web-signup-enabled/.AUTH_MODE=admin_only_email; report dir web-admin-only-email/.management-web/.When adding a new web auth mode: Add a Playwright config (e.g. playwright.<mode>.config.ts), a spec-order file if needed (e.g. e2e-spec-order-web-<mode>.txt), and include the new run in both e2e_test_report and e2e_test in makefiles/local/Makefile.local.e2e.mk (new report dir, npm run with the new config, echo/open, and exit check). Update scripts/e2e-html-steps-reporter.ts so the new output dir gets a distinct report title.
The full E2E report displays tests in conceptual order so the HTML report is easier to review (e.g. home first, then buckets list/detail/settings, then events/users/admins). Playwright may run spec files in its own order (e.g. alphabetical); when E2E_SPEC_ORDER is set (as the Makefile does from the order files), the custom HTML reporter reorders this.runs for display so the report reflects the intended order.
makefiles/local/e2e-spec-order-web.txt — one spec path per line (e.g. e2e/home-unauthenticated.spec.ts) for apps/web (default).makefiles/local/e2e-spec-order-web-admin-only-email.txt — same for apps/web admin-only-email mode.makefiles/local/e2e-spec-order-management-web.txt — same for apps/management-web.# and blank lines in the order files are ignored when building the spec list.When running one or more specs via e2e_test_web_report_spec, e2e_test_management_web_report_spec, or e2e_test_report_scoped with multiple comma-separated paths:
E2E_SPEC_ORDER from the parameter (comma → semicolon); the reporter reorders runs for display so the report shows tests in the same order as the parameter (SPEC, WEB_SPEC, or MGMT_SPEC), even if Playwright runs specs in a different order.scripts/e2e-html-steps-reporter.ts) reads E2E_SPEC_ORDER (semicolon-separated spec paths) in onEnd and sorts this.runs by that order before generating the HTML, so report display matches the intended order regardless of Playwright execution order.