Repository navigation
test: add websocket and http functional tests - #600
Merged
Merged
Conversation
- Share production app wiring with end-to-end tests and strengthen existing assertions - Rework connection lifecycle and device bindings, disconnect slow clients, unify request errors and remove unused protocol - Fix private hand exposure, dev-mode access, VP enrichment races, duplicate selections, seat overpayment and bonus tag scaling
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
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.
tl;dr: Adds functional tests that drive the real server over HTTP and real WebSocket connections, and fixes the bugs they found. Backend coverage goes from 66.8% to 78.7%; the WebSocket layer from 12% to 82%.
Details
The server wiring moves into
internal/appsomainand the newtest/e2esuites run exactly the same server.test/e2eharness and suites:-race; every HTTP routeErrorPayload, which names the failed request; the frontend's error handlers match on itcreate-gameandjoin-gameaction-success,full-state, and the client-sendableplayer-disconnectedandspectator-disconnectedtest/helperspackagetestutilreturns copies of cardsjust backend testnow runs with-race -shuffle=on; test logging is quiet by default