Sprint 2 verification record¶
Executed 14 September 2026 in this workspace.
| Check | Result | Scope |
|---|---|---|
Frontend npm.cmd test -- --reporter=dot |
42 passed across 6 files | UI/component/helper/proxy tests; mocked application HTTP methods |
API npm.cmd test -- --reporter=dot |
356 passed; 11 skipped; 29 files passed and 2 skipped | Unit and Express route tests; dedicated PostgreSQL suites were not enabled |
Frontend/API npm.cmd run lint |
Passed | Existing ESLint configurations |
Frontend npm.cmd run build |
Passed | Production bundle; existing >500kB chunk warning remains |
API npx.cmd prisma validate and npm.cmd run build |
Passed | Schema validation and Prisma Client generation |
API node prisma/check-connection.js |
Database reachable; corrected application/course reads pass | Read-only shared database; recovered migration checksum matches; migrate status up to date; schema diff empty |
Docs python -m mkdocs build --strict |
Not run successfully: MkDocs is not installed | Documentation build remains unverified in this environment |
New tests cover student application/mark UI, organiser mark verification and reasoned approval, blocked unverified approvals, withdrawal, API error display, confirmed removal/history failure, authentication/role/ownership boundaries, invalid hours/reason, closed/duplicate applications, marks, availability, clashes, hours, staffing, missing sessions, terminal states and transaction configuration. Course deletion tests cover linked historical records; allocation tests enforce override reasons. Existing fixtures now explicitly represent verified marks.
The API suite uses the real Express routes, validation and business logic with a mocked Prisma client for course applications. It does not prove PostgreSQL locking, transaction rollback, concurrent approvals or live Auth0 token exchange. Follow the acceptance script and add isolated PostgreSQL application tests before claiming extensive end-to-end coverage.
Run commands in the appropriate repository after installing its locked dependencies. npm works in ordinary shells; Windows PowerShell in this environment requires npm.cmd because npm.ps1 is disabled. Do not change machine execution policy merely to run npm. API PostgreSQL test suites document their opt-in environment variables in their source; use a dedicated test database, not the school's shared records.
Policy: feature changes affecting workflows need useful success/failure/role tests; bug fixes need a reproducer where practical. CI must fail on test/lint/build failures. Record skips and actual logs. A deployment is not accepted until the public URL, authentication, role journeys and database migration history have been checked. Link user findings to tracker issues, implemented changes and retests using the process in the Sprint 2 audit.