0.32.8_fix_tests

This commit is contained in:
Mateusz Gruszczyński committed 2026-10-14 21:58:32 +02:00
1 parent 6987b3ce33
commit bbfa8cbc3f
4 files changed
+212 -176

No files matched your search

+37
View File
@@ -49,3 +49,40 @@ schema or dashboard JavaScript event handlers were changed.
`dev.sh`; `./dev.sh test` now runs Cargo validation and the Rust test suite.
Independent API, stress, browser and real-runtime acceptance tests must be
run externally when required.
## Test-suite maintenance follow-up (0.32.8)
This maintenance change affects test code and duplicate test helpers only. No
production Rust or Go source logic was changed.
- Renamed the invalid Rust test identifier beginning with `304_` to
`response_304_with_private_policy_discards_cached_representation`. The
revalidation regression itself is retained.
- Placed four passive-health regression tests back inside the existing
`src/balance/tests.rs` `mod tests` scope, so they can use its private
`settings(HealthMode)` fixture. No test assertions were removed.
- Removed two byte-for-byte duplicate files under `scripts/tests/`:
`test_stream_tcp.py` and `test_stream_udp.py`. The canonical scripts under
`scripts/` remain, including their documented commands and self-tests.
- Statically enumerated 655 Rust `#[test]`/`#[tokio::test]` cases after the
edit, without duplicate test names or remaining numeric-leading test names.
A name containing an old version or `legacy` is not evidence that its
compatibility/regression coverage is obsolete.
**Checks passing in the available environment:**
- `python3 scripts/preflight.py`, `bash dev.sh doctor`, `bash dev.sh repair`.
- `go test ./...` in `docker-agent/`.
- `python3 scripts/test_stream_tcp.py selftest` and
`python3 scripts/test_stream_udp.py selftest` (mock-peer harness checks only;
these do not exercise RustProxy).
- Python AST parsing of all 14 scripts under `scripts/`, shell syntax checks
for `dev.sh` and the Stream/dependency helper scripts.
- All eight bundled SQLite migrations executed twice in order on an in-memory
database, with `PRAGMA integrity_check = ok` after both passes.
**Not verified:** The environment does not have `cargo` or `rustc`, and DNS
resolution is unavailable for downloading a toolchain. Consequently,
`cargo check --locked --all-targets` and `cargo test --locked --all-targets`
have not passed here. This maintenance does not close the live-runtime
acceptance gate or establish that every remaining test is passing.