Junyi Qi
Résumé

BlamePhysics · Multiplayer QA

Testing a six-player browser game

A practical multiplayer QA plan grounded in BlamePhysics’s original six-player capture, with checks for readiness, cargo, and reconnection.

BlamePhysics test capture with six players and an on-screen notice for the first cargo delivery.
Original six-player test capture from the BlamePhysics repository.

Read the capture as evidence

The original six-player BlamePhysics capture shows a crew roster, a shared goal, and the first successful cargo delivery. Those cues describe different kinds of state. The roster says who is present. The quota says what the group is trying to accomplish. The delivery notice tells the viewer which event just changed the objective.

A single frame captures one client’s view at one moment. A multiplayer QA plan can build on that evidence by recording several clients around the same transition and checking what each of them displays. The project case includes the original capture and describes the lobby, match, and reconnect flows.

Exercise the room before starting the match

Room membership, individual readiness, and the start of play are separate conditions. A useful test starts with six browser sessions in one room, changes readiness one player at a time, and checks each participant’s roster. Once the round starts, capture the room and match views so a reviewer can see whether all clients made the same transition.

Repeat the setup with the documented minimum of three players. The cases exercise different roster densities and let a reviewer look for layout issues as well as state issues. Repeat with English and Simplified Chinese if the test is also meant to catch clipped labels or unclear status messages.

Credit the delivery once across the crew

BlamePhysics includes a two-person lift. A QA pass can start with one player attempting the lift, then have a second player join and drop away. Record what each lifter sees when their contribution becomes active and whether another participant can tell that the cargo still needs help.

After the first successful delivery, compare the shared total on several clients. Sorting Quay gives another observable check because the route markers and delivery bays identify where each package should go. Dispatch Court shows separate bay states in the published capture. Review the original map captures.

Keep recovery in the same test plan

Reconnection and same-room rematches are documented interface flows. Treat recovery as part of the test session. Disconnect one participant while the remaining crew makes progress, reconnect, and compare the returned player’s room and delivery state with the other clients. Then start a rematch and check that the room membership and the new round’s objective are each correct.

Three observations to record on every client
  1. Which players are in the room and which are marked ready.
  2. The delivered count immediately before and after a delivery.
  3. The room, current objective, and delivered count after a reconnect.