User Testing

Introduction

In the absence of unit testing, user testing has been developed to verify functionality as well as capture valuable metrics that lead to improvements in the game development process. This page contains the user testing plans and results for Sprint 2, focusing on various UI features including the resource count display, dialogue box, splash screen buttons and cutscenes.

User Testing Plan

User testing was conducted by allowing testers to play the game for a maximum of 5 minutes, then completing a google form to provide feedback on the UI elements to be tested. As the game isn't fully playable functionality wise and the tests aim to gather users opinions on the design of UI features, a short testing time of 5 minutes was chosen. As the gameplay extends, the testing time will be further extended to include user testing of gameplay elements.

Link to google form: https://docs.google.com/forms/d/e/1FAIpQLSdrP-OZsyTJvzUoJ46IPVQkZCMf6gZVqANtm4yk3sFw7sbyIw/viewform?usp=sf_link

Dialogue Boxes:

Users will view the dialogue box in the running game, and will then be asked to 'dismiss' the dialogue box. The user's opinions were then recorded in the afore-mentioned Google survey.

Resource labels:

Users will view the resource labels in the game, and interact with it indirectly. They will be asked to evaluate the functionality and style in the google survey.

Cutscenes:

Users will view the opening cutscenes of the game before proceeding to the main game. They will be asked to evaluate the style and understanding of the story setting in the google survey.

Buttons:

Users will observe the buttons on the splash screen of the main game. They will start or exit the game during a gameplay launch instance and will be asked to evaluate the functionality and style of the buttons in the splash screen.

User Test Results