CodeVetter · Repo Unpack · Testing signals
keystonejs/keystone
Tests and CI were inspected, not executed; test existence and workflow commands do not establish passing results. The inspected coverage includes access control, authentication, asset lifecycle, editor behavior, CLI artifacts, and browser deletion feedback across several frameworks and database providers. This is a bounded inventory, with explicit suite exclusions and local coverage limits rather than exhaustive coverage claims.
- Vitest has a default 10-second timeout and excludes examples/testing and tests2; separate root scripts run document-package Vitest tests, Admin UI tests, tsc, filter verification, and node:test.
- API CI shards general tests across PostgreSQL, SQLite, and MySQL/MariaDB, excludes fields/crud.test.ts from those shards, and runs field CRUD separately for each provider.
- tests2/access.create.test.ts uses node:test and strict assertions to check list create denial, field create/read behavior, and privileged persisted values; its field cases skip lists containing unique fields.
- auth-header.test.ts exercises unauthenticated query/update behavior, rejects nonunique identity configuration, and verifies bearer-token access after password login.
- File tests verify bytes and metadata with in-memory storage plus replacement/deletion cleanup; these inspected cases exercise strategy doubles rather than a live S3 service.
- Document heading tests call editor.insertText()/insertBreak() and compare inline snapshots; the architecture guide describes normalization/input tests with UI rendering as smoke coverage.
- Admin UI tests combine Vitest and Playwright to check successful, failed, and partial bulk-deletion notifications; CI installs Chromium and runs selected Admin UI files with one worker.
- CLI tests cover missing builds, ESM builds, --no-prisma, and production NODE_ENV; inspected limits include manually triggered Windows CI and docs builds ignoring TypeScript errors while root tsc excludes docs.