Skip to content

Unit Selection & Information Box: User Testing

JiashengLi edited this page Aug 27, 2022 · 14 revisions

Propose for Testing

Why we start user testing

For the non-direct interaction entity which is our information box, information interaction is usually more important than real-time feedback. Players don't usually spend a lot of time interacting with an information box - because it doesn't animate like workers or buildings.

However, for a part of the overall UI, the information box is the most interactive content, players will spend more attention to read the effective information. This requires our products to have additional artistic, layout capabilities and the ability to dynamically process data visualizations.

Since most of the information and units design are not yet complete in sprint 1, we only test the product form, interface and design concept as a starting point to get our design ideas on the right path from the beginning.

Test Tasks

What we want through the test

This user testing plan is based on its generation and interactive behavior at moment.

Generation:

  • Test the size and generation position of the information box.
  • Test the product's appearance design and the degree of fit with the overall style of the game.
  • Test whether the appearance of the product will favorably or unfavorably affect the physical layout of other teams.

Interactive behavior:

  • Test whether the information in the box is easy to read and whether it saves users more time according to user habits.
  • Test if the information box is additionally triggered by mishandling and if there are potential bugs preventing the box generation.

Key Questions for Testing

Test Method: Interview

  1. Do you think the size of the information box is too large/too small?
  2. Compared with the usual RTS games, do you feel any different features of our products?
  3. How do you evaluate the art design of the information box?
  4. In a game with the theme of the sinking of Atlantis, is its art design up to standard?
  5. Do you think the generation of information box will hinder you from experiencing other game content?
  6. Have you encountered any difficulties in reading unit information? (Do you think our typography is counter-intuitive?)
  7. Did you encounter any unexpected results (any accidental touches or jams) when spawning/destroying information boxes?

Testing result

User1:

  • --

User2:

  • --

User3:

  • --

User4:

  • --

Result Ananlysis & Conclusion

--

Table of Contents

Home

Game

Game Home

Design Influences

Gameplay Features

Style

Story

Friendly Units
Map
City
Buildings
Unit Selections

Spell

Game User Testing: Theme of Unit Selection & Spell System

UI User Testing

Tutorial

Resource Stats Display

Loading Screen Bar

Health Bars
In Game menu
  • Feature
  • User Testing:In Game Menu

Landscape Tile Design

Landscape Tile Design Feedback

Weather Design

Weather Design Feedback

Camera Movement

Enemy design

Enemy Units

Enemy AI

How Animation Works

Map Flooding

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