fix: unset NODE_ENV in e2e job so devDependencies install #19

Merged
bermudalamb merged 2 commits from fix/e2e-devdeps-and-summarize into main 2026-08-15 08:56:27 -05:00
2 Commits
Author SHA1 Message Date
bermudalamb d87179363e Merge branch 'main' into fix/e2e-devdeps-and-summarize
SonarQube Analysis / sonarqube (pull_request) Successful in 7m28s
Tests / backend-unit (pull_request) Successful in 2m26s
Tests / backend-integration (pull_request) Failing after 6m39s
Tests / frontend-e2e (pull_request) Failing after 13m54s
2026-08-15 08:56:11 -05:00
bermudalambandClaude Opus 5 abebb3eb9b fix: unset NODE_ENV in e2e job so devDependencies install
SonarQube Analysis / sonarqube (pull_request) Successful in 12m1s
Tests / backend-unit (pull_request) Successful in 1m31s
Tests / backend-integration (pull_request) Successful in 2m30s
Tests / frontend-e2e (pull_request) Failing after 10m8s
npm treats NODE_ENV=production as --omit=dev, so `npm install` in the
frontend-e2e job skipped typescript and the build died on `tsc: not found`.
The same env var would have stripped vite and @playwright/test from the
frontend install, and flipped the session cookie to Secure on a run served
over plain http.

The reported summarize crash was a symptom: the job aborted before Playwright
ran, but Summarize is `if: always()` and threw ENOENT on the missing JSON,
burying the real failure. Both summarize scripts now report the missing file
and exit 0 -- the job still fails via its own step.

Also split build from start, replaced `sleep 3` with a readiness poll against
/api/config, and dump the backend log when e2e fails.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-15 08:54:07 -05:00