Monitoring settings (Sentry, Umami) and the CSP origins come from the build environment

One build per environment: PROD_* variables for the production artifact,
TEST_* for the test build and the CSP check. The build fails when a variable
is empty. Tests use the production values from config/monitoringTestEnv.ts.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-18 19:29:51 +01:00
co-authored by Claude Sonnet 5.5
parent 6475696709
commit 49b1d5f0ba
14 changed files with 286 additions and 85 deletions
+2
View File
@@ -1,4 +1,5 @@
import { defineConfig } from 'vitest/config';
import { monitoringTestEnv } from './config/monitoringTestEnv.ts';
// Browsertests (BR-TST-05, BR-TST-06) tegen de gebouwde site in dist/client.
// Los van vite.config.ts: de Start-plugin en de jsdom-opzet van de
@@ -8,6 +9,7 @@ export default defineConfig({
resolve: { tsconfigPaths: true },
test: {
environment: 'node',
env: monitoringTestEnv,
include: ['e2e/**/*.e2e.ts'],
// De CI-runner (Raspberry Pi) is veel trager dan een pc: Chrome starten
// en een pagina hydrateren kost daar vele seconden. Tests die alle 11