mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-10-02 13:39:41 +02:00
session-routes-workspace-hooks.test.ts wrote its h1/box/10.0.0.5 host fixture into getDataDir()/remote-hosts.json. getDataDir() resolves via homedir() → ~/.codeman (INSTANCE_SUFFIX='' by default), and overriding HOME in test/setup.ts does NOT change os.homedir() on Linux — so every full-suite run silently overwrote the PRODUCTION remote-hosts.json, wiping user-defined remote hosts, emptying the launch-case dropdown and breaking remote session creation (found live 2026-08-29). The vitest v4 test.env config key is ignored (probe confirmed the worker still saw CODEMAN_DATA_DIR=undefined), so the reliable fix is stubbing the env inside the test: the fixture write now goes to a throwaway /tmp dir via vi.stubEnv + finally unstub. Verified: prod remote-hosts.json hash is identical before and after the suite run.
38 lines
1.4 KiB
TypeScript
38 lines
1.4 KiB
TypeScript
import { resolve } from 'node:path';
|
|
import { defineConfig, configDefaults } from 'vitest/config';
|
|
import { NON_CI_TEST_GLOBS } from './test-suites';
|
|
|
|
const root = resolve(import.meta.dirname, '..');
|
|
|
|
/**
|
|
* The default gate — what `npm test` and CI both run.
|
|
*
|
|
* Same as vitest.config.ts but EXCLUDES the suites that cannot pass on an
|
|
* arbitrary machine: browser-driven (Playwright + chromium), visual-regression
|
|
* (per-machine PNG baselines) and wall-clock perf. Those are not unmaintained;
|
|
* they have their own runners (`test:browser`, `test:mobile`, `test:perf`).
|
|
* See config/test-suites.ts for the list and the reason behind each entry.
|
|
*
|
|
* Keep the rest in sync with config/vitest.config.ts.
|
|
*/
|
|
export default defineConfig({
|
|
test: {
|
|
root,
|
|
globals: true,
|
|
environment: 'node',
|
|
include: ['test/**/*.test.ts'],
|
|
exclude: [...configDefaults.exclude, ...NON_CI_TEST_GLOBS],
|
|
setupFiles: ['./test/setup.ts'],
|
|
// SAFETY: force every worker's data dir away from prod `~/.codeman`. Route
|
|
// tests (e.g. session-routes-workspace-hooks) write remote-hosts.json into
|
|
// `getDataDir()`; without this a bare run clobbers the production host
|
|
// registry (found 2026-08-29). `/tmp` is fine here — the tree is throwaway.
|
|
env: {
|
|
CODEMAN_DATA_DIR: '/tmp/codeman-vitest-data',
|
|
},
|
|
fileParallelism: false,
|
|
testTimeout: 30000,
|
|
teardownTimeout: 60000,
|
|
},
|
|
});
|