This document discusses approaches for testing multiplayer games. It recommends focusing tests on key areas like gameplay functionality, synchronization between clients, and different client platforms. A variety of automated testing techniques are presented, including unit, integration, end-to-end and UI testing using frameworks like Puppeteer. Both backend game server and client functionality should be tested, including approaches that use fake servers and clients. Non-automated testing like exploratory testing is also still important.

1. MULTIPLAYER
GAME TESTING IN
ACTIONS

2. Yevhen Rudiev
• QA Automation Lead at
GamePoint
• 7 years experience in IT
• 4 years experience in Automated
Testing
• Founder of Game Unit Lab
organization

3. GAMES

9. GAMES
MULTIPLAYER

10. GAME
SERVER
DB
DESKTOP
CLIENT
WEB
CLIENT
MOBILE
CLIENT
PAYMENTPLATFORM
DB DB

11. ENTERPRIS
E
SERVER
DB
DESKTOP
CLIENT
WEB
CLIENT
MOBILE
CLIENT
PAYMENTPLATFORM
DB DB

12. CLIENTS

13. CLIENTS

14. CLIENTS

15. MAIN FOCUSES
• Interesting
• Easy to play
• Fast
• Beautiful
• Stable
• Synchronized

18. GAME
SERVER
DB
DESKTOP
CLIENT
WEB
CLIENT
MOBILE
CLIENT
PAYMENTPLATFORM
DB DB

19. MANUAL
END2END
SYSTEM
UNIT

20. UNIT TESTS

21. LEGACY CODE

22. REFACTORING

23. REFACTORING

24. SYSTEM TESTS

25. GAME SERVER

26. GAME
SERVER
CLIENT CLIENT
CLIENT
CLIENT
CLIENT
CLIENT
CLIENT CLIENT

27. DIFFERENCE
ORDINARY BACK-END GAME SERVER
VS

28. ENTERPRISE
SERVER
CLIENT
REST API
COMMUNICATION

29. GAME
SERVER
CLIENT
SOCKET API
COMMUNICATION

30. SOCKET

31. GAME
SERVER
CLIENT
SOCKET API
REST API

32. SOCKET

33. OWN TOOLS

34. FUNCTIONAL TESTS

35. GAME
SERVER
DB
CLIENT
FUNCTIONAL TESTS

36. GAME
SERVER
DB
TEST
FUNCTIONAL TESTS

37. SINGLEPLAYER

38. GAME
SERVER
DB
TEST
SINGLEPLAYER FLOW
PLAYER

39. public class Player
{
public int Id {get; set;}
public string Name {get; set;}
public string Password {get; set;}
private SocketClient Client {get;}
public void Login()
{
Client.Send(new Message(Protocol.C_LOGIN, this.Id, this.Password));
Client.MessageReceived(Protocol.S_LOGIN_OK);
}
}
PLAYER

40. [Test]
public void PlayerSetStatus_Away_Positive()
{
Given().PlayerLoggedIn();
When().Message(new Message(Protocol.C_SET_PERSONAL_MESSAGE, Status.Away))
.WasSent();
Then().MessageWithConditionReceived(Protocol.S_SET_PERSONAL_MESSAGE,
msg => msg.Value == Status.Away)
.DBEntityIsRecorded(entity => entity.PlayerId == Context.Current.Player.Id &&
entity.Status == Status.Away.ToString());
}
SINGLEPLAYER

41. MULTIPLAYER

42. GAME
SERVER
DB
TEST
MULTIPLAYER FLOW
PLAYER
PLAYER

43. [Test]
public void OpponentSetStatus_Playing_Positive_PlayerReceivedOpponentStatus()
{
Given().Opponents(1)
.OpponentLoggedIn(Context.Current.Opponents[0])
.PlayerLoggedIn();
When().Message(new Message(Protocol.C_SET_PERSONAL_MESSAGE, Status.Playing))
.WasSentBy(Context.Current.Opponents[0]);
Then().MessageWithConditionReceivedBy(Context.Current.Player,
Protocol.S_SET_PERSONAL_MESSAGE,
msg => msg.Value == Status.Playing.ToString());
}
MULTIPLAYER

44. GAME
SERVER
DB
TEST
SYNCHRONIZATION
PLAYER
PLAYER

45. ADMIN’S TESTS

46. GAME
SERVER
DB
TEST
ADMIN FLOW
PLAYER
ADMIN

47. GAME
SERVER
DB
TEST
ADMIN FLOW
PLAYER
PLAYER
ADMIN

48. [Test]
public void AdminBanPlayer_Success()
{
Given().PlayerIsAdmin()
.Opponents(1)
.OpponentLoggedIn(Context.Current.Opponents[0])
.PlayerLoggedIn();
When().Message(new Message(Protocol.C_BAN, Context.Current.Opponents[0].Id, “Reason: You was bad!”))
.WasSentBy(Context.Current.Player);
Then().MessageWithConditionReceivedBy(Context.Current.Opponents[0],
Protocol.S_BAN, msg => msg.Value == “Reason: You was bad!”)
.DBEntityIsRecorded(entity => entity.PlayerId == Context.Current.Opponents[0].Id &&
entity.Status == Status.Banned, entity.Reason == “Reason: You was bad!”);
}
ADMIN

49. DEPENDENT FLOWS
PLAYER
LOGIN
SEARCHING FOR A
OPPONENT
OPPONENT
LOGIN
ENTER INTO A
GAME
PLAY GAME
SEARCHING FOR A
OPPONENT

50. DEPENDENT FLOWS
PLAY AGAIN
ENTER INTO A
GAME
END GAME
LOSE
PLAY GAME
WIN

51. FEATURE BASED TESTS

52. [Test]
public void ClassicGame_PositiveScenario()
{
Given().Opponents(1)
.OpponentLoggedIn(Context.Current.Opponents[0])
.PlayerLoggedIn();
Feature<ClassicModeGame>()
.PlayerEntersToGame_Success(Context.Current.Player)
.PlayerEntersToGame_Success(Context.Current.Opponents[0])
.TwoPlayersAreReady_GameIsStarted()
.PlayerMakeWrongTurn_ScoreWasDescreased(Context.Current.Player)
.PlayerMakeGoodTurn_ScoreWasIncreased(Context.Current.Opponents[0])
.GameTimeWasFinished_ResultsWereReceived();
}
FEATURE BASED TESTS

53. GAME
SERVER
TEST
PARALLEL PROCESSING
P
P
TEST
P
P
TEST
P
TEST
P
TEST
P
P
TEST
P P
TEST
P P
A

54. CLIENT

55. CLIENT

56. DIFFERENCE
• Technologies

57. DIFFERENCE

58. DIFFERENCE

59. DIFFERENCE
• Technologies
• Test Frameworks

60. TEST FRAMEWORKS

61. TEST FRAMEWORKS

62. TEST FRAMEWORKS

63. TEST FRAMEWORKS

64. PUPPETRY
https://www.youtube.com/watch?v=miO5-jmOZPc

65. PUPPETRY
• Click
• SendKeys
• DragTo
• Swipe
• GetComponent
• GetCoordinates
• Count

66. public class LoginScreen
{
GameObject nameField = new GameObject(“Canvas”, “nameField”);
GameObject passwordField = new GameObject(“Canvas”, “passwordField”);
GameObject loginButton = new GameObject().ByUPath(“//Canvas//loginButton”);
public MainManuScreen MakeSuccessLogin(string name, string password)
{
nameField.SendKeys(name);
passwordField.SendKeys(password);
loginButton.Click();
return new MainMenuScreen();
}
}
PUPPETRY

67. TEST
[Test]
public void Login_CorrectCredentials_Success()
{
//Arrange
var name = "Yevhen";
var password = “SeleniumCamp2019";
//Act
var screen = new LoginScreen().MakeSuccessLogin(name, password);
//Assert
Assert.IsTrue(screen.IsScreenOpened,
$"Main Menu was not opened after login with {name} and {password}")
}

68. FUNCTIONAL UI TESTS

69. GAME
SERVER
CLIENT
APPROACH
TEST

70. CLIENT
APPROACH
TEST

71. TESTS
• CRUD tests
• Functional tests

72. GAME
SERVER
CLIENT
APPROACH
TEST

73. GAME
SERVER
FAKE
CLIENT
APPROACH
TEST

74. PLATFORMS

75. COMMON LOGIC

76. CUSTOM LOGIC

77. OTHER PLAYER RELATED UI

78. GAME
SERVER
FAKE
CLIENT
SOCKET API
OPPONENT
TEST CLIENT

79. GAME
SERVER
FAKE
CLIENT
FAKE CONTROLLER
TEST
REST API
SOCKET API

80. FAKE
REST
CONTROLLER
CONNECTION
CONNECTION MANAGER
CLIENT TEST

81. public class ScenarioBuilder
{
public ScenarioBuilder MakeSuccessLogin_MainManuIsLoaded()
{
Context.Current.Page = new LoginScreen()
.MakeSuccessLogin()
.IsLoaded();
return this;
}
public ScenarioBuilder StartPlayGame_SearchingForOpponentWasStarted()
{
Context.Current.Page = ((MainMenuScreen)Context.Current.Page)
.ClickPlayGameButton()
.SearchingForOpponentMessageIsShown();
return this;
}
}
PLAYER SCENARIO

82. END2END TESTS

83. GAME
SERVER
DB
CLIENT
PAYMENTPLATFORM
DB DB
TEST

84. GAME
SERVER
DB
CLIENT
PAYMENTPLATFORM
DB DB
TEST

85. GAME
SERVER
DB
CLIENT
PAYMENTPLATFORM
DB DB
TEST

86. GAME
SERVER
DB
CLIENT
PAYMENTPLATFORM
DB DB
TEST

87. LACK OF TECHNOLOGIES

88. CROSSBREEDING

89. CROSSBREEDING
• Puppetry + Appium

90. GAME
SERVER
DB
MOBILE
CLIENT
TEST
APPIUM
PUPPETR
YOPPONENT

91. CROSSBREEDING
• Puppetry + Appium
• Puppetry + Selenium

92. MANUAL TESTING

93. MANUAL TESTING
• New functionality
• Functionality that hard to automate
• Exploratory testing
• Layout and visual testing
• Testing of sounds
• Localization testing

94. WHAT’S NEXT?
• Performance testing of Game Server
• Performance testing of Client
• Visual testing
• Bot for exploratory testing

95. CONCLUSION
• Games are not usual enterprise application, but
have a lot of common
• You can re-use common approaches
• You can invent your own approaches

96. CONTACTS:
www.linkedin.com/in/yevhen-rudiev-a5609590
www.facebook.com/evgeniy.rudev.5
yrudiev@gmail.com
@gameunitlab