prod-smoke-test

Run an end-to-end production smoke test that validates a deployed multiplayer game release by exercising full game phases across phone, laptop, and automated browser sessions, confirming no disconnects or server errors occur.

A production smoke test for a multiplayer game validates post-deploy health by running a full 9-player match from room creation through final victory, while monitoring backend logs, browser console telemetry, audio events, and WebSocket stability.

Run a post-deploy smoke test after a docker compose restart by triggering an automated end-to-end game flow across phone, laptop, and browser sessions, which reports a clear go or no-go result based on game phase completion.

Yes, you need live backend access and SSH-driven bot control to run the automated browser smoke test, which coordinates VM-driven bot actions and monitors WebSocket stability during the multiplayer game run.

An end-to-end production smoke test catches broken logins, room setup issues, phase transition failures, unexpected disconnects, and hidden server errors before you declare a multiplayer game release successful.