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
+11 -1
View File
@@ -1,4 +1,4 @@
import { describe, expect, it } from 'vitest';
import { afterEach, describe, expect, it, vi } from 'vitest';
import { contentSecurityPolicy, securityHeaders } from './securityHeaders';
const umami = 'https://analytics.slpsoftware.nl';
@@ -12,7 +12,17 @@ const captchaFrames = [
const directive = (csp: string, name: string) =>
csp.split('; ').find((d) => d.startsWith(name + ' ')) ?? '';
afterEach(() => vi.unstubAllEnvs());
describe('securityHeaders', () => {
it('noemt Umami en Sentry niet zonder monitoringinstellingen in de build', () => {
vi.stubEnv('VITE_SENTRY_DSN', '');
const csp = contentSecurityPolicy('production');
expect(csp).not.toContain(umami);
expect(csp).not.toContain(sentry);
expect(directive(csp, 'script-src')).toBe("script-src 'self'");
});
it('productie-CSP heeft geen onveilige uitzonderingen voor scripts', () => {
const csp = contentSecurityPolicy('production');
expect(csp).not.toContain('unsafe-eval');