ЄВГЕН РУДЄВ «Multiplayer game testing in actions» QADay 2019
Download as PPT, PDF0 likes592 views
The document discusses multiplayer game testing, emphasizing the unique aspects of game server architecture compared to traditional backend systems. It highlights various testing approaches including manual, functional, and automated tests, alongside specific functionalities and processes for multiplayer games. Additionally, it touches upon future testing plans and the importance of adopting both common and tailored methodologies for game applications.
![[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](https://image.slidesharecdn.com/rudev-190417224727/85/Multiplayer-game-testing-in-actions-QADay-2019-41-320.jpg)
![[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](https://image.slidesharecdn.com/rudev-190417224727/85/Multiplayer-game-testing-in-actions-QADay-2019-44-320.jpg)
![[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 BASEDTESTS](https://image.slidesharecdn.com/rudev-190417224727/85/Multiplayer-game-testing-in-actions-QADay-2019-49-320.jpg)
![TEST
[Test]
public void Login_CorrectCredentials_Success()
{
//Arrange
var name = "Yevhen";
var password = “BAQ_2019";
//Act
var screen = new LoginScreen().MakeSuccessLogin(name, password);
//Assert
Assert.IsTrue(screen.IsScreenOpened,
$"Main Menu was not opened after login with {name} and {password}")
}](https://image.slidesharecdn.com/rudev-190417224727/85/Multiplayer-game-testing-in-actions-QADay-2019-64-320.jpg)
ЄВГЕН РУДЄВ «Multiplayer game testing in actions» QADay 2019
- 2. Yevhen Rudiev • QA Tech Lead at Trading Tool Solutions • 7 years experience in IT • 4 years experience in Automated Testing • Founder of Test Unit Lab organization
- 3. GAMES
- 12. CLIENTS
- 13. CLIENTS
- 14. CLIENTS
- 15. MAIN FOCUSES • Interesting • Easy to play • Fast • Beautiful • Stable • Synchronized
- 20. UNIT TESTS
- 21. LEGACY CODE
- 22. REFACTORING
- 23. REFACTORING
- 24. SYSTEMTESTS
- 25. GAME SERVER
- 27. DIFFERENCE ORDINARY BACK-END GAME SERVER VS
- 30. SOCKET
- 32. SOCKET
- 33. OWN TOOLS
- 34. public class SocketClient { public void StartConnection(IpAddress address, int port) { } public void Send(Message message) { } public void MessageReceived(int messageId) { } public void MessageWithConditionReceived<T>(int messageId, Func<bool> condition) { } public void MessageWasNotReceived(int messageId) { } public void MessageWithConditionWasNotReceived<T> (int messageId, Func<bool> condition) { } } OWN TOOLS
- 35. FUNCTIONAL TESTS
- 38. SINGLEPLAYER
- 40. 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
- 41. [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
- 42. MULTIPLAYER
- 44. [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
- 46. DEPENDENT FLOWS
- 51. CLIENT
- 52. CLIENT
- 54. DIFFERENCE
- 55. DIFFERENCE
- 56. DIFFERENCE • Technologies • Test Frameworks
- 57. TEST FRAMEWORKS
- 58. TEST FRAMEWORKS
- 59. TEST FRAMEWORKS
- 60. TEST FRAMEWORKS
- 62. PUPPETRY • Click • SendKeys • DragTo • Swipe • GetComponent • GetCoordinates • Count
- 63. 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
- 64. TEST [Test] public void Login_CorrectCredentials_Success() { //Arrange var name = "Yevhen"; var password = “BAQ_2019"; //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. TESTS • CRUD tests • Functional tests
- 71. PLATFORMS
- 72. COMMON LOGIC
- 73. CUSTOMLOGIC
- 74. OTHER PLAYER RELATED UI
- 78. 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; } } PLAYERSCENARIO
- 79. END2ENDTESTS
- 85. CROSSBREEDING
- 86. CROSSBREEDING • Puppetry + Appium
- 88. CROSSBREEDING • Puppetry + Appium • Puppetry + Selenium
- 89. MANUAL TESTING
- 90. MANUAL TESTING • New functionality • Functionality that hard to automate • Exploratory testing • Layout and visual testing • Testing of sounds • Localization testing
- 91. WHAT’S NEXT? • Performance testing of Game Server • Performance testing of Client • Visual testing • Bot for exploratory testing
- 92. 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