Sam Sung
927f0117fb
The test gates ran `cargo test`, which runs the workspace's test binaries one after another. On a warm tree the workspace's tests take 103 s that way, and 59 s under cargo-nextest, which runs every binary's tests in one pool; all 10,411 pass both ways. `check.sh` and `gates.sh` now run tests through `scripts/unit-tests.sh`: cargo-nextest where it is installed, else `cargo test` as before. nextest runs no doctests, so `scripts/doc-tests.sh` runs those of the library crates in scope. Each gate keeps its environment (`BENILLA_REQUIRE_DATA`, `WOW_DATA=`, the skip log), and a failing run's summary now catches nextest's `FAIL` lines. CI is unchanged. Test: this land's own gates run under it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 lines
694 B
Bash
Executable File
14 lines
694 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# The test gates' runner: the tests of every target the cargo package and target flags it is given
|
|
# select, all run, a failure not stopping the rest. Under cargo-nextest where it is installed, which
|
|
# runs every test binary's tests in one pool (the workspace takes 59 s to `cargo test`'s 103 s on a
|
|
# warm tree, M4 Max); else `cargo test`. nextest runs no doctests: `scripts/doc-tests.sh` does.
|
|
#
|
|
# scripts/unit-tests.sh --workspace
|
|
# scripts/unit-tests.sh -p benilla-app --no-default-features --lib
|
|
set -euo pipefail
|
|
if cargo nextest --version >/dev/null 2>&1; then
|
|
exec cargo nextest run --no-fail-fast --no-tests=pass "$@"
|
|
fi
|
|
exec cargo test --no-fail-fast "$@"
|