docs(testing): match determinism, scenario and taxonomy text to the code (10-07)
The strategy doc promised clock/random/scheduler helpers that no test used (the helper's clearTimeout did nothing), listed three scenario IDs the catalog does not have, and the taxonomy described an older test:all and a child-process rule tests/unit does not follow. Removes the unused helper. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
d68e25a2ad
commit
84f2ab929f
@@ -16,9 +16,11 @@ Each gate is blocking in its declared scope. Failures are not downgraded with
|
||||
| end-to-end | `pnpm test:e2e` | pinned browser engines | `artifacts/tests/e2e/` |
|
||||
| accessibility | `pnpm test:a11y` | pinned browser engines | `artifacts/tests/a11y.json` |
|
||||
|
||||
`test:all` is the normal product-development loop. It intentionally includes
|
||||
runtime-schema, unit, capability-contract, component, integration, reference
|
||||
feature and recipe suites, but does not include `test:system`. CI-runner and
|
||||
`test:all` is the normal product-development loop. It runs, in order,
|
||||
`test:runtime-schema`, `test:unit`, `test:contract`, `test:component`,
|
||||
`test:integration`, `test:reference-feature`, `test:platform` (`tests/platform`
|
||||
and `tests/architecture`), `check:release-coherence` and `test:recipes`
|
||||
(`package.json` `test:all`). It does not include `test:system`. CI-runner and
|
||||
supply-chain assurance has different host prerequisites and is invoked
|
||||
explicitly in the assurance path.
|
||||
|
||||
@@ -82,11 +84,19 @@ CI / release assurance:
|
||||
|
||||
A host-level process/sandbox test must not be placed in `tests/unit` merely
|
||||
because it uses Vitest. The classification follows the system boundary and
|
||||
prerequisites, not the test framework. Process-heavy tests that spawn child
|
||||
processes but do not require privileged host facilities belong in
|
||||
`tests/integration`; for example the provider guardian transaction protocol
|
||||
lives at `tests/integration/provider-guardian-transaction.test.ts`. Its
|
||||
handshake timeout is a test watchdog, not a production protocol deadline.
|
||||
prerequisites, not the test framework:
|
||||
|
||||
- Tests that need systemd, bubblewrap, cgroup v2 or CI-provider process
|
||||
controls belong in `tests/system`.
|
||||
- Tests of a long-lived child-process protocol belong in `tests/integration`;
|
||||
for example the provider guardian transaction protocol lives at
|
||||
`tests/integration/provider-guardian-transaction.test.ts`. Its handshake
|
||||
timeout is a test watchdog, not a production protocol deadline.
|
||||
- A script's own tests may start that script, Node or Vitest as a short-lived
|
||||
child process to check its command-line contract, and stay in `tests/unit`
|
||||
next to the script's other tests. Such a suite declares its own longer
|
||||
timeout instead of raising the global one; for example
|
||||
`tests/unit/risk-coverage.test.ts` uses `PROCESS_HEAVY_TIMEOUT_MS`.
|
||||
|
||||
End-to-end and automated accessibility scenarios run on the pinned Chromium,
|
||||
Firefox, and WebKit engines. The responsive contract explicitly exercises
|
||||
|
||||
Reference in New Issue
Block a user