Root cause of fake connections in Usage (zed-live-*@example.com, guard-*@example.com, zed "Account N", kimchi-nope): route-level tests (zed-live-models, zed-native-auth) call createProviderConnection, which persists to $DATA_DIR/db/data.sqlite. With DATA_DIR unset — the default for `npx vitest run` — that resolved to the user's real ~/.9router DB, appending test rows on every run. Both files documented "RUN WITH AN ISOLATED DB" but never enforced it. Add tests/setup/isolateDataDir.js (wired via vitest setupFiles) that points DATA_DIR at a throwaway temp dir before src/lib/dataDir.js is imported. Opt out with RUN_REAL=1 or an explicit DATA_DIR (used by the *.real.test.js suites that read live credentials). Verified: a full suite run now leaves the real DB byte-count unchanged; new guard test tests/unit/test-data-dir-isolation.test.js locks it in.
34 lines
1.4 KiB
JavaScript
34 lines
1.4 KiB
JavaScript
import { defineConfig } from "vitest/config";
|
|
import { resolve } from "path";
|
|
import { fileURLToPath } from "url";
|
|
|
|
const __dirname = fileURLToPath(new URL(".", import.meta.url));
|
|
|
|
export default defineConfig({
|
|
test: {
|
|
environment: "node",
|
|
globals: true,
|
|
include: ["**/*.test.js"],
|
|
// Redirect DATA_DIR to a throwaway temp dir so route-level tests that call
|
|
// createProviderConnection never touch the user's real ~/.9router DB.
|
|
// RUN_REAL=1 or an explicit DATA_DIR opts out (see setup/isolateDataDir.js).
|
|
setupFiles: ["./setup/isolateDataDir.js"],
|
|
// Don't scan into git worktrees nested under .claude/ — they carry their
|
|
// own copies of the test files but lack an installed node_modules (open-sse,
|
|
// etc.), which makes provider imports fail during collection.
|
|
exclude: ["**/node_modules/**", "**/.claude/**", "**/dist/**"],
|
|
// Allow many it.concurrent cases (real provider smoke runs ~50 providers in parallel)
|
|
maxConcurrency: 60,
|
|
// Suppress noisy console output from handlers under test
|
|
silent: false,
|
|
},
|
|
resolve: {
|
|
// Use array form so subpath aliases (e.g. "@/lib/db/index.js") resolve correctly.
|
|
alias: [
|
|
{ find: /^open-sse\//, replacement: resolve(__dirname, "../open-sse") + "/" },
|
|
{ find: "open-sse", replacement: resolve(__dirname, "../open-sse") },
|
|
{ find: /^@\//, replacement: resolve(__dirname, "../src") + "/" },
|
|
],
|
|
},
|
|
});
|