Files
orca/config/vitest.config.ts
T
NeilandOrca e8d4818b5a test(env): keep happy-dom MutationObserver callbacks alive across GC (#12438)
happy-dom holds each observer's internal callback in a WeakRef, so a GC pause
under sharded CI load permanently kills a still-connected observer. That is what
made the activity portal readiness test flake: once the observer died, no amount
of re-applying ready DOM could release the latch.

Co-authored-by: Orca <help@stably.ai>
2026-08-03 23:18:15 -07:00

39 lines
1.3 KiB
TypeScript

import { resolve } from 'node:path'
import { defineConfig } from 'vitest/config'
const windowsTestWorkerOptions = process.platform === 'win32' ? { maxWorkers: 4 } : {}
export default defineConfig({
define: {
ORCA_FEATURE_WALL_ENABLED: 'true'
},
resolve: {
alias: {
'@renderer': resolve('src/renderer/src'),
'@': resolve('src/renderer/src')
}
},
test: {
environment: 'node',
// Why: Node 26's undefined Web Storage globals prevent Vitest from installing happy-dom's.
execArgv: ['--no-experimental-webstorage'],
// Why: happy-dom drops MutationObserver callbacks on GC; keep them alive like a browser does.
setupFiles: [resolve('config/scripts/happy-dom-mutation-observer-retention.ts')],
include: [
'src/**/*.test.ts',
'src/**/*.test.tsx',
'config/scripts/**/*.test.ts',
'config/scripts/**/*.test.mjs',
'tests/tools/**/*.test.mjs',
'tests/e2e/**/*.unit.test.ts'
],
// Why: the full suite runs heavy TS transforms plus real git/http fixtures;
// the Vitest 5s defaults are too tight for the slowest integration cases.
hookTimeout: 60_000,
testTimeout: 30_000,
// Why: Windows process and shell startup are slower under full-suite load;
// macOS/Linux keep Vitest's default worker parallelism.
...windowsTestWorkerOptions
}
})