Files
deepseek-harness/vitest.config.ts
T
Tianyi Cui 1a1ce734ba feat(acp-example): add record/replay llm/stream plugin for snapshot tests
Introduces examples/acp-agent/src/llm-replay.ts, a function/namespace plugin
that installs a single llm/stream waterfall listener. In record mode it tees
the real model's StreamChunks into a per-scenario llm.json (flushed atomically
after EACH stream, since the snapshot subprocess is SIGKILLed and start.ts has
no disposal path). In replay mode it short-circuits the waterfall and serves
recorded streams back positionally — the Nth stream() call gets the Nth entry —
so a snapshot test can drive the real agent with no API key.

Each fixture entry is a discriminated record {chunks|throw|hang} so it can
replay BOTH branches of the LLM failure contract (throw from stream() vs a
finish-error chunk) plus cancellation. A throw entry carries the prefix chunks
emitted before the throw, replayed before the error, so a mid-stream failure
(partial output then STREAM_CLOSED) reproduces what the loop saw live.

Fail-loud on a missing or exhausted fixture (never a silent skip). Unit tests
drive the real LlmService waterfall (record tee, ordered replay, the three
entry kinds, partial-then-throw, fail-loud, event-driven abort, HMR-safety).
Broadens the unit vitest include to examples/*/tests and registers the plugin
+ snapshot tests as knip entries. Per docs/rfc/implemented/2026-06-19.
2026-06-19 01:10:30 +08:00

44 lines
2.1 KiB
TypeScript

import tsconfigPaths from 'vite-tsconfig-paths'
import { defineConfig } from 'vitest/config'
export default defineConfig({
// Vite ≥8 warns that this plugin can be replaced by the native (experimental)
// `resolve.tsconfigPaths: true`. It cannot — keep the plugin. Tests run
// unbuilt (see AGENTS.md): bare workspace names like `cordis` or
// `@deepseek-ai/dsh-llm` must resolve to src/, and the only place that
// mapping exists is the root tsconfig.json `paths` map inherited by
// tsconfig.test.json. The native option is a bare boolean: for each
// importing file it discovers the NEAREST tsconfig.json and applies that
// file's own `paths`. Every workspace under packages/* and vendor/* has its
// own tsconfig.json without `paths`, so native resolution maps nothing,
// falls through to package.json exports (lib/, absent until `pnpm run build`),
// and every test file fails to import (verified on vite 8.0.16 /
// vitest 4.1.8). Making it work would mean copying the paths map into all
// 15 workspace tsconfigs — including vendor/* ones, which are pinned
// upstream copies (vendor/README.md). The plugin's `projects` option
// instead applies the one root map to every importer.
plugins: [tsconfigPaths({ projects: ['./tsconfig.test.json'] })],
test: {
include: ['packages/*/tests/**/*.spec.ts', 'examples/*/tests/**/*.spec.ts'],
coverage: {
provider: 'v8',
// Coverage measures OUR runtime source. Types-only files carry no
// executable code; vendor/ and examples/ are out of scope (examples are
// exercised by the demo smoke test instead).
include: ['packages/*/src/**/*.ts'],
exclude: ['packages/*/src/types.ts'],
// 100% or it doesn't merge (AGENTS.md: excessive tests are welcome).
// Per-file so a well-covered big file can't subsidize a bare one.
// Every v8 ignore comment must carry a reason — see AGENTS.md.
thresholds: {
perFile: true,
statements: 100,
branches: 100,
functions: 100,
lines: 100,
},
reporter: ['text', 'html'],
},
},
})