Add two client connection QA gate
This commit is contained in:
@@ -49,3 +49,25 @@ Required evidence:
|
||||
|
||||
This gate is server-relevant and requires multiplayer server verification when
|
||||
server launch tooling or deployed package contents change.
|
||||
|
||||
## Two-Client Connection
|
||||
|
||||
The two-client connection gate proves the MVP can be tested as a multiplayer
|
||||
session with two packaged Windows clients connected to the same Ground Zero
|
||||
server.
|
||||
|
||||
Required evidence:
|
||||
|
||||
- The server launch gate is passing.
|
||||
- `Scripts/RunTwoClientConnectionSmoke-Windows.bat --check-tools` confirms the
|
||||
packaged client exists.
|
||||
- The helper launches two clients against the same endpoint:
|
||||
`play.agrariangame.com:7777` by default, or a supplied LAN endpoint such as
|
||||
`192.168.5.15:7777`.
|
||||
- Both clients reach the same Ground Zero session.
|
||||
- Testers confirm both clients see the same time/weather and can remain
|
||||
connected long enough to begin the smoke test.
|
||||
|
||||
The manual observation steps continue in
|
||||
`Docs/Ops/MultiplayerLatencyTestPlan.md` until gameplay automation can drive
|
||||
two clients directly.
|
||||
|
||||
Reference in New Issue
Block a user