Notes on testing

We recommend doing any testing in two stages. In (1) integration testing you test the general functionality of your integration. This includes authentication, connectivity through websockets, and if required, integration into external hosting providers. In (2) performance testing, the behavior of the matchmaker under realistic load is tested.

(1) Integration testing
For this initial stage, the matchmaker remains in its standard configuration with a target waiting time' of 1 sec. and no further configurations. This is significantly shorter than anyone would use in production, but simplifies the testing of whether all components are integrated.

(2) Performance testing
Once the integration is tested and you have customized the matchmaker (see Customize Matchmaker), you can start testing the behavior of the matchmaker in a production-like environment. We recommend setting the 'target waiting time' to a value of 20-30 sec., which is a range that many games settle on (see Target-waiting-time). The matchmaker learns and adjusts to the inflow of players queuing (e.g. distribution of skills). Therefore, we recommend testing with an inflow of players of >1 players/sec. for a duration of 30min. If your game is very popular, testing with 5-10/sec might be advisable, to get representative results.