Skip to content

Sprint 4 Testing and Validation

LungYuLin edited this page Oct 17, 2022 · 13 revisions

Link back to main page

Throughout sprint 4 we aimed to polish the remaining main features of ranged enemies which were tested to maintain user and studio satisfaction as seen below.

Design Test Plan

The following test progression was followed to ensure consistent testing was achieved throughout the sprint

  • Conduct external testing
  • Make changes to any problems that were highlighted during testing

Design User Testing

Design Studio Validation

External Testing and Validation

Eel External Testing

Starfish External User Testing-1

Starfish External User Testing-2

Code Test Plan

Prototype Testing:

J-Unit Tests

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