Skip to content

Commit 5bef6fa

Browse files
committed
docs(vitest): drop the resolved subprocess-spawn testing note
The list, mutation exclusion, and #1823 outcome already live on SUBPROCESS_STUB_TESTS / SERIALIZED_TESTS. testing.md should not copy a closed experiment once the files are ordinary unit-core members.
1 parent 3bdb15c commit 5bef6fa

1 file changed

Lines changed: 0 additions & 8 deletions

File tree

‎docs/agents/testing.md‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -162,14 +162,6 @@ Lock plans come from the production request-lock decisions — never hand-author
162162
modeled boundary is documented in the harness module, and every failure prints its exact replay
163163
command.
164164

165-
## Real-subprocess-spawn tests
166-
167-
`SUBPROCESS_STUB_TESTS` enumerates the few files that spawn a real subprocess per case. #1823's kill
168-
criterion was met, so the `subprocess-stub` project is gone: these files now run un-serialized in
169-
`unit-core`'s default forks pool. The list survives solely as mutation-lane exclusion
170-
(`SERIALIZED_TESTS`): a real per-case spawn is timeout noise under thousands of mutant reruns. There
171-
is no unit-test retry layer — fix or remove flakes.
172-
173165
## Speed rules
174166

175167
- Unit tests do not wait production time. Prefer budget-derived cadence, assert the caller passes

0 commit comments

Comments
 (0)