Skip to content

Team 4 Testing Plan Sprint 4

Ari Bowe edited this page Oct 20, 2021 · 9 revisions

Unit Testing

PlayerActionsTest

A simple test was added to PlayerActions which checked if isPlayerDead returns the correct value when the player is alive. This test creates a simple Player object, and checks the value of isPlayerDead that was set upon creation.

User Testing

Overall User Testing

In this sprint, our team did not conduct any user testing as our main priority was reformatting the wiki, simple player movement improvements, and cleaning up previous code.

Potential areas for user testing concern the simple player movement improvements made. A simple user test could involve having the user run through the game with the updated player movement, and then with the updated player movement. Observations regarding the user's completion time and death count could be made to indicate the success of the changes. Additionally, the user could be asked a series of questions following the gameplay to determine their thoughts about the differences in movement.

  1. Which game did you find easier (improved or non-improved)? Why?
  2. What aspects of the players updated movement would you change further?
  3. Which aspects of the obstacles did you find hardest to complete with the improved movement? How does this compare to the non-improved movement?

etc...

Updated Level Design User Testing

During this sprint, a task based user test was conducted for level 2 and 3 to determine the functionality of the implemented interactive elements in gameplay.

The participants were asked to complement 3 tasks, including:

  1. Unlock a door by pressing the button.
  2. Activate the bridge by pressing the button.
  3. Complete the level by reaching the portal.

No data for this user test was taken, as it was purely observation-based.

However, from the observations made during this user test, all participants were able to easily complete the 3 given tasks.

Through this test, we were able to determine that the functionality of the interactive elements is adequate for the current game. Some suggestions to improve the current elements included, creating different views for the button to allow it to lie flat on the floor obstacles instead of being upright. These suggestions will be taken into consideration in the future.

Table of Contents

Home


Game Design

Game Design Document

Void/Antivirus

Loading Screen

Game Sound

Menu Assets

Player Design

     Original Design

     Final Design


Gameplay

Movement

Jumping & Sliding

Jump Pads

Portals & Bridges

Buttons

Pick-Ups

Physics

    Momentum & Physics

    Gravity

    Collision


Level Design

Level 1

     Background

     Textures

     Map Design

Level 2

     Background

     Textures

     Map Design

Level 3

     Background

     Textures

     Map Design

Level 4

     Background

     Textures

     Map Design


Sprint Round-Up

Sprint 1 Summary

Sprint 2 Summary

Sprint 3 Summary

Sprint 4 Summary


User Testing

Testing Plans

Sprint 1

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 2

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 3

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 4

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

User Testing

Sprint 1

     Sprint 1 - Game Audio
     Sprint 1 - Character Design
     Sprint 1 - Menu Assets
     Sprint 1 - Map Design
     Sprint 1 - Void

Sprint 2

     Sprint 2 - Game Audio
     Sprint 2 - Character Design
     Sprint 2 - Menu Assets
     Sprint 2 - Interactable Design Animation
     Sprint 2 - Levels 1 & 4, and Level Editor
     Sprint 2 - Proposed Level 2 & 3 Designs
     Sprint 2 - Current Game State

Sprint 3

     Sprint 3 - Menu Assets
     Sprint 3 - Map Design
     Sprint 3 - Score Display
     Sprint 3 - Player Death and Spawn Animations
     Sprint 3 - Pick Ups and Pause Screen

Sprint 4

     Sprint 4 - Gameplay
     Sprint 4 - Game UI and Animation
     Sprint 4 - Level Background and Music
     Sprint 4 - Game User Testing
     Sprint 4 - Final Game State Testing


Game Engine

Entities and Components

     Status Components
     Event System
     Player Animations Implementation

Level Editor

Level Saving and Loading

Status Effect


Defunct

Development Resources

    Getting Started

Entities and Components

    Level Editor (Saving and Loading
         Multiple Levels)

    Service Locator

    Loading Resources

    Logging

    Unit Testing

    Debug Terminal

Input Handling

    UI

    Level Saving/Loading

    Status Effects

    Animations

    Audio

    AI

    Physics

Game Screens and Areas

    Terrain

    Concurrency & Threading

    Settings


Troubleshooting

MacOS Setup Guide

Clone this wiki locally