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 Santiago Fernandes to test certain parts of it. I shall be a test buddy for......

Here are the tests:-

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

 

his is my welcome page. When players start my game this will be the first thing they see. As you can see at the bottom of the picture when you press the space button the game will start.

Test 2: The game must be error-free.

 

My game is error free because it does everything I want it to do. However I could have made improvements to my work and I had ideas that I could not replicate onto my work due to a lack of Scratch knowledge in some areas. I am pleased however on how I completed my work as I had a problem where my previous game did not save.

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

 

 

In my game I have two variables. One for time and one for how many points you get. In my time variable I made it so after thirty seconds it would go to my “Game Over” background. My points variable I made it that every time my “character” touched one of my fruit sprites one point would be added.

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.

 

  

I am happy with my blog because I have been posting useful information about scratch for myself and for the public. I also used some other information like fun tricks that you can do on websites such as YouTube and Facebook, I think that has helped me to get over 130 views on my blog.

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

 

 

My sprites do not bulge or slim because my game is not like that, however I have named each one of my sprites accordingly. My sprites are fruits so I named the sprites the name of the fruit.

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

In my game I have a point counter as seen on the right of the picture; this shows how many times I have collected a fruit by my character.

Test 7: Does my Game Over page tell me what my final score is?

  

 Yes, when 30 seconds finish the game will change to this background so you will know the game is finished and what your final score is.

Test 8: Are my backgrounds labelled correctly?

 

 

I think that my backgrounds are labeled correctly because each ones name represents its purpose. The Welcome Menu tells you the instructions and what the games about. The Game area is the actual game, and finally the Game Over background tells you the games over and what your final score is.

Test 9: How do the fruits move around.

 

 

With my fruits I thought to make it more exciting I would make them move around a bit randomly so you have fun when trying to catch them. I made them move 5 steps because I found that any higher was too fast for my liking and any lower was too slow. I also put in “if on edge bounce” so that the fruits are constantly moving and always in the game.

Test 10: Is my Sprites movement at a good speed?

 

I wanted my sprites movement to be at a considerate speed because if it was too fast everything would be too confusing and if it was too slow it would be boring. So I settled on having my sprite on “move 10 steps” this way I could catch up to the fruits and have fun.