Skip to content

Sprint 2 Inventory System and Consumables User Testing (Team 8)

Bohankkk edited this page Sep 13, 2022 · 19 revisions

Test Content

A demo of the inventory system and consumables item completed in Sprint 2.

Test Objectives

  • Understand how users interact with products;
  • Find out how satisfied users are with the section;
  • Find out if users can understand the usage of the design behind the product;
  • Identify modifications needed to improve product usability issues.

Test Plan

This user test will use questionnaires and remote testing to obtain feedback data.

  • Questionnaires: The questionnaire consisted of 5 short answer questions. The design framework of the questionnaire will be clear and concise, and will ensure that each question has good clarity.
  • Remote testing: The remote testing uses Zoom shared screens to present the demo, conduct interviews, and gather key points from the testing.

Participants

  • The questionnaire will have 10 participants.
  • The remote test will have 3 participants.
  • All participants were volunteered to participate in this test.

Testing Results

Questionnaires:

Screen Shot 2022-09-14 at 12 21 00 am Screen Shot 2022-09-14 at 12 21 06 am Screen Shot 2022-09-14 at 12 21 14 am

Remote Testing Notes:

Screen Shot 2022-09-14 at 12 48 16 am

Analyse Results

Based on questionnaires and remote testing data, we found that 50% of the participants were neutral about our design, and 30% of the participants were dissatisfied with the demo, when they stand at the point of potential users. We believe that the reasons for the following results are:

  • The interaction design part still needs to be improved;

For instance, we can add more interaction design into the inventory system. And also add more interactive elements on consumables items.

  • The colour matching and layout of the inventory system are not good enough;
  • The icons of some consumables are not clear enough;

The Icons of consumables are not a good representation of the meaning of their functions.

Therefore, based on these three aspects, we will continue iterate and extend this part in Sprint 2 and the next few Sprints. And we will also pick some critical suggestions from users remote testing to make the overall demo look more user-friendly.

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
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