-
Notifications
You must be signed in to change notification settings - Fork 0
Unit Testing
polyrain edited this page Aug 1, 2021
·
1 revision
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.
- Player UI
- Popup Menus
- Obstacles
- Boss Enemies
- Progress Tracker
- Checkpoint Design and Functionality
- Score System
- Lives System
- Game Background
- Multiple game-level
- Visual Improvements
- Tutorial Level
- Character Design and Animations
- Character Damage Animations
- Player Animation Functionalities
- Player and Serpent Portal Transition
- Pop-up Menus
- Obstacles
- Lives & Score User Testing
- Buffs & Debuffs
- Buffs & Debuffs redesign
- Obstacle Animation
- Background Design
- Level 2 Background Appearance
- Enemy Monster User Testing
- Level 1 Floor Terrain Testing
- Introduction Screens User Testing
- Character Movement Interviews & User Testing
- Sound user testing
- Level 2 Obstacles and enemy
- Story, Loading, Level 4 and Win Condition Sound Design User Testing
- Giant Bug and Purple Squid animation user testing
- General Gameplay and Tutorial Level User Testing
- Level 4 Terrain User Testing
- Game Outro User Testing