You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/test.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ title: "Tests"
14
14
-`OPENCLAW_TEST_CHANGED_BROAD=1 pnpm test:changed`: explicit broad changed test run. Use it when a test harness/config/package edit should fall back to Vitest's broader changed-test behavior.
15
15
-`pnpm changed:lanes`: shows the architectural lanes triggered by the diff against `origin/main`.
16
16
-`pnpm check:changed`: runs the smart changed check gate for the diff against `origin/main`. It runs typecheck, lint, and guard commands for the affected architectural lanes, but does not run Vitest tests. Use `pnpm test:changed` or explicit `pnpm test <target>` for test proof.
17
-
- Rust workspace changes route through active-toolchain `cargo fmt --all --check`, `cargo package -p sparsekernel-core --locked`, `cargo clippy --workspace --all-targets --locked -- -D warnings`, and `cargo test --workspace --locked` locally; CI runs the same Rust lane with Rust 1.80.0 to enforce the workspace MSRV.
17
+
- Rust workspace changes route through active-toolchain `cargo fmt --all --check`, `cargo package -p sparsekernel-core --locked --allow-dirty`, `cargo clippy --workspace --all-targets --locked -- -D warnings`, and `cargo test --workspace --locked` locally; CI runs the clean package equivalent with Rust 1.80.0 to enforce the workspace MSRV.
18
18
-`pnpm test`: routes explicit file/directory targets through scoped Vitest lanes. Untargeted runs use fixed shard groups and expand to leaf configs for local parallel execution; the extension group always expands to the per-extension shard configs instead of one giant root-project process.
19
19
- Test wrapper runs end with a short `[test] passed|failed|skipped ... in ...` summary. Vitest's own duration line stays the per-shard detail.
20
20
- Full, extension, and include-pattern shard runs update local timing data in `.artifacts/vitest-shard-timings.json`; later whole-config runs use those timings to balance slow and fast shards. Include-pattern CI shards append the shard name to the timing key, which keeps filtered shard timings visible without replacing whole-config timing data. Set `OPENCLAW_TEST_PROJECTS_TIMINGS=0` to ignore the local timing artifact.
0 commit comments