Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@smoogipoo
Copy link
Contributor

@smoogipoo smoogipoo commented Sep 24, 2025

Maybe this will help a bit?

Most of matchmaking is intended to be tested via TestMultiplayerClient.ChangeMatchRoomState() and designing the appropriate state to test your objects with.
This change primarily adds TestMultiplayerClient.MatchmakingChangeStage() which acts as a helper for components that just need the current stage + the countdown for it. The biggest changes are to TestSceneMatchmakingScreen and TestSceneMatchmakingScreenStack.

Interspersed are a few more minor changes including 597a06a + 83dafb4 which together help to bring the room into a correct initial state, and 3556d6c which reduces the number of picks shown in test scenes to a more realistic value (8 users per room, not 50).

@smoogipoo smoogipoo added area:test coverage Adds or modifies test coverage without adding any functionality. area:multiplayer labels Sep 24, 2025
@peppy peppy self-requested a review September 24, 2025 06:48
@peppy peppy merged commit 93afc83 into ppy:master Sep 24, 2025
6 of 9 checks passed
@peppy peppy deleted the improve-mm-testing branch September 24, 2025 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:multiplayer area:test coverage Adds or modifies test coverage without adding any functionality. size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants