test: license-free .NET wire-contract tests for guest auth models#23
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #21 (guest auth). #21 merged before this test commit landed, so these tests never made it onto main - this PR adds them.
Why
The Unity CI jobs (PlayMode smoke, EditMode) are skipped in this repo because there is no
UNITY_LICENSE, so the guest auth added in #21 has no automated coverage in CI. This adds coverage to the one job that DOES run without a license: the standalone.NETtest project (Tests/AsobiCore.NET).What
Runtime/Models/AuthModels.csin the.NETtest project.AuthModelsTests.cs: pins the guest wire contract -GuestRequest->{device_id, device_secret},GuestUpgradeRequest->{username, password}, andAuthResponseparsing of thecreated/guest/upgradedflags (create vs resume vs upgrade), including that absent flags default to false.At runtime the SDK serializes with
UnityEngine.JsonUtility, which maps public fields to their literal names.System.Text.JsonwithIncludeFieldsreproduces that mapping for these flat POCOs, so a field rename fails the build the same way it would break the wire.Local validation
dotnet test Tests/AsobiCore.NET-> 40 passed, 0 failed (35 existing dispatch tests + 5 new). Runs headless, no Unity license, no backend.