Code Testing

Introduction

In accordance with the [Test Plan] (./Software-Test-Plam) tests were written for the ResourceCostComponent and the TrapComponent. Furthermore, greater emphasis was placed upon user testing which was undertaken to gain feedback in relation to the upgradeStructure, and handleBuildingDestruction methods.

Tests

TrapComponentTest

Requirement	Test case addressed by
Test entities are damaged by trap	ShouldTrap
Test entities with the wrong hitbox layer are not damaged by trap	shouldNotTrapOtherLayer
Test entities without a combat component are not trapped	shouldNotTrapWithoutCombatComponent

ResourceCostComponentTest

Requirement	Test case addressed by
Test the cost of buildings is returned correctly	shouldGetResources

User Testing

To fairly conduct user testing, the following assumptions were made:

• The player would be provided with a control scheme outlining all game controls (the assumption being this is a UI element which has not yet been included in the game)
• The player would be given an outline of the game, and its win conditions
• The user would be provided a goal to achieve within the game

Players were given the following goals to complete within the game, and feedback was collected during and after observation:

• Create one of each of the buildable structures
• Destroy buildings
• Upgrade buildings

Reflection