GAME TESTING STRATEGY & PLAN

I will test my game to make sure it works while I create it. I will also test it after I have finished coding to make sure it works fully as planned. I shall do the testing myself but I shall also ask Cameron to test certain parts of it. I shall be a test buddy for Cameron

Here are the tests:-

Test 1:  The game must have clear instructions for the user.

Test 2: The game must be error-free.

Test 3: The game must have the meaningful variables of ….

Test 4: The game must be documented well in my blog so that I can come back to it at a later date to make alterations to it if needed.

Test 5: Each collecting sprite needs to have 3 states:- normal, bulging, slim and named appropriately.

Test 6: The program has to keep a score of all the collected sprites.

Test 7: to see if the speech works

Test 8: to see if you can go from one side of the screen to the other straight away.

Test 9: to see if the controls work

Test 10: to see if the variables work

TESTING

Add screenshots to each of the test items above as evidence that you have tested them. For each test, explain the various states of the program (e.g. show what happens when the score increases).

It is OK to include tests for the test items above that DO NOT work. Some parts not working are the normal part of the process. You need to be honest. Explain what you would do to fix it if you had more time

EVALUATE In your blog, evaluate how well your game works. What are its strengths? How could you improve it further if you had more time?