| Filename | Latest commit message | Latest commit date |
|---|---|---|
Soul could not construct a selection where To.SchemaId decides the EdgesFor/page_edges order once From, Role and To.RecordKey already tie, but flagged that as a claim, not a proof - the same shape of argument that was wrong twice before on this comparator (R-AT). Traced instead of asserted: TryResolveReferenceTarget (C#) and resolve_reference_target (Rust) resolve a reference purely from the citer's schema, the role, and the record key, against the evaluation's own fixed candidate index (byKey/by_key) - no edge- or caller-specific input steers which candidate wins. Once From and Role tie (pinning the citer's schema and the declared target type/leaves) and To.RecordKey also ties, the resolved row - schema included - is forced identical by construction, in both runtimes, every time. No mutation can distinguish it because no input can, so it was deleted rather than recorded as "equivalent": a component nothing can distinguish is a line every future reader must reason about for no behavioural gain. Deletes the To.Descriptor.SchemaId/to.schema_id() ThenBy/then_with from CultNetSelectionEvaluator.EdgesFor and selection.rs's page_edges sort, and updates the comments (in-code and the Survivor 5 test block) that described the old five-key chain. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
| .. | ||
| CultNetCanonicalNumberTests.cs | ||
| CultNetDocumentBindingResolverTests.cs | ||
| CultNetOperationServerTests.cs | ||
| CultNetSchemaContractTests.cs | ||
| CultNetSchemaServerGroupTests.cs | ||
| CultNetSelectionEvaluatorTests.cs | ||
| CultNetSelectionFixBatchTests.cs | ||
| CultNetSelectionPageTests.cs | ||
| CultNetSelectionSurvivorTests.cs | ||
| GameCult.Networking.Tests.csproj | ||
| MiniJsonSchemaValidator.cs | ||
| NetworkingTests.cs | ||
| README.md | ||
| SelectionParityVectorTests.cs | ||
| SelectionWireParityTests.cs | ||
GameCult.Networking.Tests
GameCult.Networking.Tests contains NUnit tests for the networking library.
Scope
The tests currently cover:
- AES-GCM encrypt/decrypt round-trips in
Secret - signed session-token validation
- signed session-token tamper detection
- signed session-token expiry handling
Run
dotnet test tests\GameCult.Networking.Tests\GameCult.Networking.Tests.csproj
Adding New Tests
Typical future areas to expand include:
- client reconnect and verify flows
- login and registration integration tests
- malformed message handling
- rate-limiting behavior under concurrency