Game testing is a crucial part of the game making process. In order to make sure that the game is ready to be sold and played, it needs to be able to run smoothly and without glitches. This is one of the things I have decided to focus on for my independent component.
The other part i'm focusing on is the data checking portion. The games at Blue Marble are created to rehabilitate brain injuries and prevent falling in the elderly. So, in order to track the patients' progress, the information and results from the different games played are sent to a data base called Deep Ocean. The actions' results, that help the health professionals determine whether or not you are making progress, are recorded in Deep Ocean. There, they can access all of the information from the game under that certain username.
My job in data checking is to make sure that the data is being sent and recorded properly in the Deep Ocean. This will prevent future miscalculations in a patient's progress.
Below are some photographs of the data checking process.
1. First, I set up a camera to record the level as I play in order for me to be able to go back and check what I did. This is also just in case there is a bug that needs to be fixed. It is easier to just show on a recording than to go back and try to recreate what happened.
2. The game is pulled up on whatever device I am playing on. I sign into an account and select a level. I play the level all of the way through. The data will be sent to Deep Ocean once I finish the level and go to the level select screen.
3. After, I go back and view the recording. This way I can write down the data and compare it to what is recorded in Deep Ocean to make sure that everything is being recorded properly.