Skip to content

Unit Testing

acoox edited this page Apr 23, 2021 · 2 revisions

Most of the provided game and engine are heavily unit tested, and it is recommended that you do the same for any additions you make. Try to follow this checklist to avoid common mistakes:

  • All tests should should extend from GameExtension, using the @ExtendWith(GameExtension.class) annotation. This ensures that the correct mocking of underlying graphics is done, and that the service locator is cleared between tests.
  • When testing anything that relies on time, use ServiceLocator.getTimeSource() as your time source. Then in your tests you can provide a custom timesource with hardcoded values. You should never have tests that rely on real time passing.
  • If the code you are testing relies on the service locator, make sure you initialise the necessary services. All services will be null by default.

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