Skip to content

UI Testing

tgarnsworthy edited this page Aug 28, 2022 · 21 revisions

Testing and Validation

Testing was conducted on users that fit the target audience, which was university students, that enjoy playing video games. Two types of testing were conducted to measure the success of UI implementations.

  • User Testing One: Simply Button Design
  • User Testing Two: Navigational Testing

User Testing One: Simple Button Design

This user testing was used to determine the colours, size and general look of the buttons, and how users feel when looking at them. The user testing method that was deemed appropriate for the goal of this test was Contextual inquiry. This means that this user test was run as a general real-time interview. Four users were tested using the simple interview method. Below are the starting questions I used.

Questions That Were Asked:

  • What are the first 3 things that catch your eye?
  • Do you feel that any of the buttons stand out?
  • Do you think they are all intuitive?
  • If you could change one thing what would it be? These were the main questions that the conversation was built from.

Alterations from Testing:

From the interviews there was three changes that had to be made:

  • The Cogs button needed adjustment as Users did not find it intuitive. The blue/green colour it was, made users question what it was for, also the illustration was said to be "not really a cog, but more of a symbol of some sorts".
  • The next change was not to do a coin bar, but rather a number of coins collected, this was a general consensus from all users as they found "you can have more than 100% in coins".
  • The last thing that needed to be changed was the music and sound buttons, when the music button is clicked it has a small amount of annimation where it goes a duller shade, but it also looks like it is instantly turned off, for consistency reasons, the music button needs to be the same. This is mainly because they will be right next to each other on the page.

User Testing Two: Navigational Testing

When the buttons were fully linked and the goals of the sprint were completed. This is essential to ensure that the navigation of the screen and the ensure that it is intuitive to find all pages. (First Click Testing)

Purpose:

Navigational testing is highly valuable to assess how potential users navigate through the game when assigned a particular end goal. Team 10 have created three tasks that are considered fundamental to sprint 1 with the implementation of buttons that link to other pages and enable changes in functionality. The results that come out of these tests help narrow down primary user flows and improve the game’s information structure.

Tests:

  1. Starting at the Start Page, can you navigate to the shop pop-up?
  2. Can you identify where the status of the crystal’s health would be displayed?
  3. Can you find two different ways to access the settings page?

Results:

Person 1:

  • Observations: User one had no issues finding any of the pages, they followed the path of the file correctly in every instance. For the first question, their first click was on the start page which brought them to the shop page. This also allowed them to easily find the settings page as they just clicked the setting on main and clicked back to go to the main menu again. The third test was very simple as well as they clicked start and found the statics in the right corner.

  • Conclusion: From this test, it was very clear that there was a mood change finding that the buttons didn't work. Obviously, satisfaction is created from pressing a button and the screen changing.

Person 2: Person 3:

Conclusions:

Table of Contents

Home

How to Play

Introduction

Game Features

Main Character

Enemies
The Final Boss

Landscape Objects

Shop
Inventory
Achievements
Camera

Crystal

Infrastructure

Audio

User Interfaces Across All Pages
Juicy UI
User Interfaces Buildings
Guidebook
[Resource Management](Resource-Management)
Map
Day and Night Cycle
Unified Grid System (UGS)
Polishing

Game Engine

Getting Started

Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally