vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-04-18 20:51:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: modernize vitest projects config

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-03 17:18:53 +01:00
parent 9dba944c42
commit 2b900b576c
12 changed files with 320 additions and 324 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/help/testing.md
View File

@@ -45,7 +45,7 @@ Think of the suites as “increasing realism” (and increasing flakiness/cost):
### Unit / integration (default)
- Command: `pnpm test`
- Config: native Vitest `projects` via `vitest.projects.config.ts` (`unit` + `boundary`)
- Config: native Vitest `projects` via `vitest.config.ts` (`unit` + `boundary`)
- Files: core/unit inventories under `src/**/*.test.ts`, `packages/**/*.test.ts`, `test/**/*.test.ts`, and the whitelisted `ui` node tests covered by `vitest.unit.config.ts`
- Scope:
- Pure unit tests
@@ -74,7 +74,7 @@ Think of the suites as “increasing realism” (and increasing flakiness/cost):
- Unit and boundary projects stay on `forks`.
- Channel, extension, and gateway configs also stay on `forks`.
- Unit, channel, and extension configs default to `isolate: false` for faster file startup.
- `pnpm test` inherits the isolation defaults from `vitest.projects.config.ts`.
- `pnpm test` inherits the isolation defaults from the root `vitest.config.ts` projects config.
- Opt back into unit-file isolation with `OPENCLAW_TEST_ISOLATE=1 pnpm test`.
- `OPENCLAW_TEST_NO_ISOLATE=0` or `OPENCLAW_TEST_NO_ISOLATE=false` also force isolated runs.
- Fast-local iteration note: