Enemy NPCs Testing Plan - UQcsse3200/2024-studio-2 GitHub Wiki

Testing Plan

Sprint 1 Test Plan

The testing plan for Sprint 1 focuses on validating key functionalities related to enemy NPCs, ensuring their correct behavior in the game. The primary areas to be tested include enemy creation, proper spawning, animation loading, player detection, and combat initiation. Specific sub-features such as enemy NPCs rising from the ground based on the player's vicinity and initiating combat upon proximity will be tested both visually and through automated unit tests.

Sprint 2 Test Plan

The test plan for Sprint 2 outlines the approach and scope for testing the latest iteration of the Enemy NPCs and functionalities and features implemented. The plan focuses on ensuring that the new features and functionality implemented during this sprint meet the required quality and functionality standards. By identifying key test areas, outlining the testing approach, and estimating resource requirements, this plan documents the testing done on these functionalities to ensure that all important aspects of this feature are thoroughly validated.

Sprint 3 Test Plan

The test plan for Sprint 3 details the strategy and scope for testing the latest iteration of the Enemy NPCs and their implemented functionalities and features. This plan is centered on verifying that the new features and functionalities introduced during this sprint, specifically regarding Enemy NPC interactions (such as the BlindBearTask and Bee spawning from hives) align with the necessary quality and performance standards. By highlighting critical test areas, outlining the testing methodology, and estimating resource needs, this document records the testing conducted on these functionalities to ensure that all significant aspects of the feature are thoroughly validated.

Sprint 4 Test Plan

The testing plan for Sprint 4 will focus on conducting a comprehensive evaluation of the game's features and finalizing all key components, with particular emphasis on enemy interactions and animations. This includes verifying the correctness of enemy stats, testing the behavior and interactions implemented in the EnemyFactory, and ensuring the StealTask functions as expected. Additionally, visual testing will be performed to validate important game screens, such as pre-combat cutscenes, to confirm that animations and transitions appear smooth and seamless. User testing will also be integrated into this sprint to gather feedback on gameplay mechanics, user experience, and overall satisfaction, ensuring that the game meets player expectations. By ensuring that all enemy-related tasks—such as animations, stats, interactions, and user feedback—are thoroughly tested, Sprint 4 aims to finalize the game and ensure all components function cohesively.