Games Testing

 Game testing is an extremely important part of game developing, and it's best to start testing as early into the process as possible.You should be trying to find all errors or areas needing improvement as soon as you can. However, there are some risks for Game Testing for example:

• If there is no fun factor
• If the Game is not unique, fast-paced or competitive
• If there are broken features or bugs 
• The game doesn’t include a player-centric design

It is important not to become too involved with the testers process, although it's temping to jump in and help if someone is struggling to progress through the game it is crucial to allow them to figure it out alone. This is to make the experience as authentic as possible as future users will not have the designer/developer there to help them. 

The 7 most popular Game Testing techniques are:

1. Functionality Testing - This is done to confirm if the end product works
2. Combinatorial Testing - Using this method you can test the game quickly in the early stages, this can help you find out if the game has any bugs
3. Ad Hoc Testing - Also called "General Testing", this is a much more informal and less structured way of testing. It doesn't follow any process or plan and needs no documentation.There are three different types of Adhoc testing; Pair testing, Buddy testing, and Monkey testing.
4. Compatibility Testing - This tests the compatibility of your game on various different devices and platforms
5. Clean Room and Tree Testing - This is to test the consistency and reliability of the software
6. Regression Testing - This is to recheck if the game is still working correctly and to see if any new bugs have come up with the changes made.
7. Performance Testing- This tests the games overall performance in real time scenarios 

(Image found on pinterest at - https://pin.it/2Yke6Vx)

Thanks for reading :)