How to test new features

We already covered briefly testing new code in Chapter 10, Eat, Sleep, Test, Repeat: Test Methodology.

Here, we will look at it exclusively from a live ops perspective. In live ops, we generally have four development tracks, as shown in Figure 11.3.

Figure 11.3 – The different types of game updates in live ops

Testing new content

The first development track is about content production. Every successful game in live ops has regular content updates. This provides players with new levels or areas of a game to play. Content usually comes out in cadence, and players learn to expect it at regular intervals. By adding new content, we keep our most loyal players engaged, and the game feels fresh and fun to play. Mature development teams have very well-organized content pipelines that are planned a couple of months ahead. The QA team’s job here is to make sure that new content works as it should and can easily be integrated...