Establish controlled red-suite baseline
This commit is contained in:
14
README.md
14
README.md
@@ -12,12 +12,13 @@ the main assembly's packet/message/asset/primitive wire-data, core
|
||||
runtime/networking, avatar-facing manager, world/social/service manager, RLV,
|
||||
LSL tools, Utilities, Vivox, and WebRTC slices now have complete callable,
|
||||
failure-only signatures. The independent downstream fixture compiles every
|
||||
cataloged type and member with zero exclusions; semantic Rust test translations
|
||||
are the next stage.
|
||||
cataloged type and member with zero exclusions, and all 1,289 NUnit invocations
|
||||
now have reviewed Rust parity cases. Production behavior implementation is the
|
||||
next stage.
|
||||
|
||||
Pending NUnit cases are inventory only, not generated fake tests. A case counts
|
||||
as translated only when an explicit Rust test body calls the mapped API and
|
||||
retains the upstream identity and body hash.
|
||||
A case counts as translated only when an explicit Rust test body calls the
|
||||
mapped API and retains the upstream identity and body hash. The parity ledger
|
||||
now contains zero pending or unreviewed cases.
|
||||
|
||||
The source snapshot, compatibility rules, dependency research, and ordered
|
||||
implementation plan are in [RUSTREWRITE.md](RUSTREWRITE.md).
|
||||
@@ -37,6 +38,7 @@ cargo test --workspace --no-run
|
||||
python3 tools/generate_rust_mapping.py --check
|
||||
python3 tools/generate_api_shims.py --check
|
||||
python3 tools/check_test_parity.py
|
||||
python3 tools/audit_red_suite.py
|
||||
```
|
||||
|
||||
`tests/upstream-tests.json` is the machine-readable NUnit parity catalog.
|
||||
@@ -46,3 +48,5 @@ verifies the catalog against the pinned adjacent LibreMetaverse checkout without
|
||||
overwriting those files.
|
||||
|
||||
Running `cargo test --workspace` is intentionally red during the shim stage.
|
||||
The controlled audit aggregates every expected failure by standardized C#
|
||||
member ID and rejects unrelated fixture, assertion, compile, or symbol errors.
|
||||
|
||||
Reference in New Issue
Block a user