Files
football2801 77f54dc6f5
CI / test (push) Has been cancelled
chore(ddev): ddev tests now also runs npm run build
So the public/build/ bundle that ships in the next deploy always matches
the source the tests just verified. Without it, the previous "Remove
this frame" feature shipped source-correct but compiled-stale, and the
button never appeared on the deployed PWA.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-08 15:50:46 -04:00

26 lines
1.0 KiB
Bash
Executable File

#!/bin/bash
## Description: Run the full test suite — PHPUnit + vitest + vue-tsc
## Usage: tests [phpunit-args]
## Example: ddev tests
## Example: ddev tests --filter test_id_tz_01
set -euo pipefail
echo "── PHP unit + integration ─────────────────────────────"
# DDEV's web_environment sets APP_ENV=dev for dev work — phpunit's xml <server>
# directive doesn't always override that cleanly, so force the env explicitly.
APP_ENV=test bin/phpunit "$@"
echo
echo "── Frontend typecheck + tests ─────────────────────────"
cd frontend
npx vue-tsc --noEmit -p tsconfig.app.json
npx vitest run
echo
echo "── Frontend production build ──────────────────────────"
# Rebuild public/build/ so what gets committed matches what passed tests.
# Without this step, deploys can ship source-correct features whose
# compiled bundle is stale (verified failure mode 2026-05-09).
npm run build