The testing process took a lot of time to go over all relevant aspects of the project with a fine-tooth comb and to attempt to ensure that all errors can be catered for. My testing was carried out in two ways :
• Whitebox testing
• Blackbox testing
- Whitebox testing
This was performed entirely by myself, The way i undertook the testing was to ensure that all aspects of my project worked. This does not mean searching for bugs, but rather the opposite, and just ensuring that the program did what it was supposed to do. This means :
• Generating an accurate terrain
• Making sure terrain textures looked correct
• Ensuring water movement gave off a realistic effect
• Comparing the current weather over SW Ireland with that in the program
• Testing the flight simulation, and pondering whether or not any sort of realism was achieved.
- Blackbox testing
With the blackbox testing, I was able to create 2 events. The first one involved myself searching through the program and trying to find errors (for example : poor collision detection, or clipping plane errors). As I coded the project, I am most likely to know where errors could possibly reside. The second type of testing involved 3 subjects; my brother, my sister and my cousin. I asked them to play the game, and give me feedback based on :
• Their perception of the project
• Learning outcome of it
• Overall enjoyment
• Amount of errors/inconsistencies they spotted
The results were as follows :
Sarah| Adam| Sean
Perception 6 7 4
Learning 2 3 4
Enjoyment 4 1 1
Errors* 5 7 7
Table 6.1 – Grading
*Scores are inversely proportional; 1 is a high amount of errors, 10 is low
As visible from above, my subjects have a low understanding of the work that goes into creating a game such as this. I think they were expecting a game more along the lines of Microsoft Flight Simulator, Or Call of Duty. So overall they weren’t hugely impressed and seemed to get bored of the game after a matter of minutes, but I’m happy enough with the grading as this is a one man project.
