Team 3 Testing Plan Sprint 3

User Testing

Purpose

The following user test aims to gather feedback regarding the new character death animation. It seeks to gain opinions regarding first impressions, suitability of the design for the theme and game narrative, and design recommendations. Results from this user test can be found here.

Process

1. Have users complete the following questionnaire to gain feedback regarding the player death animation.
2. Evaluate questionnaire responses

Questionnaire items include:

• A gif of the character being dragged away with its limbs being teared off. No background are implmented just the character and a transparent background.
• The following questions:

1. How would you rate this death animation aesthetically? (1: Not cool 5: looking good)

2. The idea behind the animation is the character being sucked into a void. Do you think the animation conveys that idea clearly?

3. If you answered no, what do you think is happening to the character instead?
4. What recommendations do you have that could improve the death animation of the character?

Question 1 This gauges the first impression of the animation to the user.

Question 2 This tests whether the initial idea behind the animation is conveying clearly to the user.

Question 3,4 These two questions ask for recommendation that can be used to improve the animation later on.

Unit testing

PlayerActionsTest

Since our feature this sprint was based around the player's animation refinement majority of the code can not be tested by unit tests since you have to visually inspect the game screen to make sure the animations are running smoothly however, we can test if the expected animation is running at a given time.

For testing purposes the function setSpawnAnimation() returns an integer either 1, 2 or 3 depending on the Math.Random() function call, we can test that if 1 is returned that the variable spawnAnimation = "spawn_level1", if 2 is returned spawnAnimation = "portal_flip" and if 3 is returned spawnAnimation = "spawn_portal"

We can also test that if the playerIsDead() function is called that the variable playerHasDied is set to true meaning the death animation has been triggered.

The last thing to test is that when the variable playerCanMove is set to false that keyboard input has no effect on the player, we can test this since when the player is created getAnimation() returns "IdleRight", so after we create the player we can set playerCanMove = false and attempt to change the player's state and then checking to see if getAnimation() returns the same string.