Designing Tests for Computer Games – Testing Suites

A testing suite is a plan laid out which describes how you are going to try to test a part of a game (one of the operating regions) for bugs.

Pre-game:For the pre-game operating region, i decided to test the login system of the game, to see if using different browsers such as firefox, chrome and internet explorer or computers could potentially trigger a bug.

whilst other people in the class have claimed to have multiple issues upon trying to log in, I experienced none myself  (or at least none until I was back in game) except for some slow performance when using internet explorer.

game start: the game start operating region is very small for this game, and as such the only way i could think to test it was to see if there was any way to break the intro movie which plays upon starting the game. I immediately encountered a bug whilst starting it with internet explorer as the player claimed that the video was unsupported. I also tested this in chrome and firefox, and in both of these browsers the video played fine. upon reporting this it turns out this is a known bug because the game hasn’t yet been properly optimised for internet explorer.

in-game: i plan on testing the tutorial section of the games cinematics and scripted sequences. i choose this section as with it being an early part of the game, i will be able to quickly return to any bug i find by creating a new account, should that be the only way to recreate it. i will try to test this by logging out during these parts or by clicking on different parts of the window to see if there is any effect on the sequences such as skipping parts out.

I did manage to find a bug whilst carrying out the tests during the “overwatch reboot” sequence, as the buttons to continue to the next part can be used before reaching the end of the animation, essentially skipping out the animation

post-game: in the post game operating region, i plan on testing whether or not the game is saved correctly. i plan on doing this in several ways. firstly, i will clear the cache and history of the browser after logging out, then logging back in, i will then  also do this using multiple browsers (such as chrome, firefox and internet explorer), and then i will try switching between different computers to see if that has any sort of effect on the save.

I tried testing the by playing in different browsers and on different computers, however any changes or progress was saved successfully.

Designing Tests for Computer Games – Testing Suites – Bug Report

The Bug I found in Year Zero is a minor bug which occurs during the In-Game operating region. The bug occurs early on in the game during the sequence which shows the “overwatch system” being rebooted (after completing the first tutorial level). The bug is only very minor as it essentially skips through the sequence similarly to skipping a cutscene, and is performed by clicking on the “Start” button at the bottom-right of the window, as well as by clicking on the “Continue” button in the same place on the next screen. this seems to be a bug because it isn’t until the animation on each screen has finished that these buttons change colour from red to green and you are actually told to push the button.This bug fits into the normal trigger category, as it is a bug in the in-game operating region and seems most likely to just be the result of an oversight. I repeated the testing of this bug several times by logging out before reaching the end of the sequence to reset it when i next logged in, and also by creating another account to see if it had been fixed in the time since reporting it (it hadn’t been).