CodeVetter · Repo Unpack · Testing signals
payloadcms/payload
Tests and CI were inspected, not executed; no passing result is asserted. Vitest separates unit, browser-component, RSC, integration, and evaluation projects, while Playwright covers browser workflows and visual comparisons. Read assertions demonstrate intended coverage of request construction, authentication, authorization, password migration, and selected accessibility behavior. The inventory and inspection are bounded, and neither test existence nor CI configuration establishes exhaustive coverage or runtime correctness.
- Vitest selects package/tool/unit specs for the Node unit project, TSX specs for Chromium component tests, and Next RSC specs under react-server resolution conditions.
- The integration project selects test/**/*int.spec.ts, disables file parallelism, uses 90-second hook/test timeouts, and loads test/vitest.setup.ts; CI configures two Vitest retries.
- Shared integration fixtures initialize/destroy Payload once per file, ordinarily reset and seed before each payload-backed test, and provide REST/SDK clients; the inspected auth suite explicitly disables between-test resets.
- Read auth assertions cover successful REST login, removal of restricted user fields from login responses, owned preference updates, first-user registration rejection, and legacy password rehashing.
- createPayloadRequest unit tests use mock Payload objects to check supplied URL precedence, configured serverURL fallback, and localhost fallback; these assertions do not exercise a real database or HTTP server.
- The inspected WCAG Playwright suite checks the login logo's accessible name and lack of tab stop, plus column-editor headings and checkbox labels; browser configuration defines only a Chromium project.
- Main CI configures unit/component/type checks and sharded integration tests; integration runs can exclude Canary-named tests when the upstream Next canary package probe reports an incomplete publish.
- Production E2E CI excludes @visual tests, which run in a separate path-gated visual job using pinned Playwright Docker tooling; the scripts and workflow were inspected, not executed, so their current outcomes and uninspected flows remain unverified.