Team 3 Sprint 3 test plan and user test

Ragnarok Racer User testing

Time:

During sprint 3

Purpose:

To find potential improvements that could be added during the next sprint

Method:

Co-design method via discord demo.

Participant profiles:

Aged 18-25, game lovers.

Rationale:

At the current point, we would call the Ragnarok racer game at least a medium-fidelity prototype, since it was playable, but some function was still needed to implement, and some detail was needed to be polished. The game was not fully ready to run locally on users’ machines easily, therefore the testing session was conducted online.

Procedure:

1. Gather the user on a discord channel.
2. Livestream the game.
3. Informing the user about the procedure
4. Do what the user told me to do
5. Let the user speak their mind while conducting the testing
6. Record the result and the feedback
7. Repeat all above for more users

Conductor:

Jiaao Yu

---

Result:

The user testing session contained 4 main tasks:

1. Read the tutorial
2. Play the game and win
3. Play the game and lose
4. Exit at any point of the game

The ideal outcome:

1. Users would understand the tutorial without any confusion
2. Users would be able to know at least the basic operations of the game
3. Users would be able to achieve either win and lose condition
4. Users would be able to exit the game at any point they want

There were 4 users who participated in user testing, the result from the different users would be labelled as user 1 to 4 in the following context.

User 1

• The UI looks retro
• The text in the tutorial page blends in the background
• The style looks different in the tutorial page
• Don’t know how to win exactly
• Doesn’t seem too dynamic when playing the game
• The buttons are not consistent

User 2

• Love the feedback when hovering and clicking on the buttons
• The animation looks weird when getting hurt
• The enemies look pretty small, it would be better if the size is increased
• Love the death screen, it looks cool.
• Cannot go back to the main page after clicking the exit button on the death screen

User 3

• The UI looks cool
• The font is not consistent
• The animation looks weird
• Don’t know how to win
• Cannot go back to the main menu at any point after starts playing the game

User 4

• Love the design of the buttons
• Don’t know what armour is
• Don’t know how to win
• Don’t know if there is a background story
• The animation looks weird, don’t think the character is moving forward
• Don’t understand the mechanism of the movement of the enemies

Analysis:

Based on the user testing result, we found that there is a lot of polish to the games that needed to be done.

Objects need to pay attention to in the next sprint:

1. The tutorial page could consider changing the font and the colour of the content, which also corresponds to our initial plan, we wanted to add more images instead of only texts at the moment.
2. The game needs more information on the tutorial page, such as the mechanism of the game, the properties of the enemies (obstacles), so that users would understand how to encounter them.
3. The style of the game needs to be consistent throughout the entire game, such as the buttons and the font should be somehow the same style in the game.
4. The game needs to be able to go back to the main menu after playing the game, instead of it is only able to exit the entire game when a user chooses to play the game.

Objects that have been taken care of already or can be ignored:

1. The size of the enemies (also obstacles) has been adjusted, and they are looking fine now.
2. A background story has been added before playing the game.
3. A timer has been added on the right top corner of the game so that users would know how to win and the remaining time.
4. Animations of the character has been implemented so that users could feel the character is moving forward, and it looks more dynamic also.