-
Notifications
You must be signed in to change notification settings - Fork 2
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.
Inventory System
Scoring System
Food Recipes
Level System
Player Actions
Ordering System
Stations
Items
Map Design
Customers
Pause Menu
Upgrades
End of Day Display
Day Night Cycle
Moral System
Debug Terminal
Game Interactions Tutorial
Backstory Cutscenes
Entities and Components
Input Handling
Game Screens and Areas
Fire Extinguisher Handler Component
MainGameActions Create Docket Triggers
Main Game Order Button Display
BackstoryCutsceneDisplay Test Plan
Test Plan for MainGameOrderTicketDisplay
Test Plan for MainGameOrderBtnDisplay
Test Plan for DocketLineDisplay
Test plan for RandomComboService
Test plan for SpeedBoostUpgrade
Test plan for DancePartyUpgrade