Testing Plan: Combat Visual Assets - UQcsse3200/2024-studio-2 GitHub Wiki

Our Testing Plan for Combat Visual Assets consists of a combination of Unit Testing and Video Testing to ensure correct functionality in both our code behind-the-scenes and appropriate and correct visual implementation of assets.

• Unit Testing: will be used to ensure all classes work effectively independent of each other. Will allow the identification of bugs and issues regarding each aspect of the visual combat screen
• Video Testing: will be used due to ease and appropriate-ness in evaluating the successful implementation of visual assets in combat screen. It is extensively completed to ensure that the functionality works not just once, but repeatedly for all UI and visual components of combat.

Test Classes

• CombatAreaTests.java

• CombatScreenTests.java (to be implemented)

• CombatTerrainFactoryTests.java (to be implemented)

• CombatStatsDisplay.java (to be implemented)

Video Testing

• Verifies correctness of listener/triggers in CombatStatsDisplay and Combat Area as well as correctness of methods in CombatStatsDisplay

• CombatInventoryDisplay visual components, rendering updates, and event trigger/listener validation

• Verification of Dialogue Box in Combat, Disappear/Reappearance of Buttons, Prevention from Exit of Combat Screen Until Dialog is Complete

• Verification of Status Bar UI with Kanga Boss

• Visual Testing of Combat Button Hover Hints, Special Move Status Effects, and General Player Combat Animations

• Visual Testing of Combat Animal Animations - Tested on the Frog Enemy

• Visual Testing for Loss Condition Against Enemy NPCs (Bug Fix)

• Visual Testing for Updating Stats Bars Correctly in Combat (Bug Fix)

• Visual Testing for Combat Stats Change Popups

• Visual Testing for Combat Animations and Sounds Synced Together