Sprint 3: Story and NPC Testing Plan - UQdeco2800/2021-studio-6 GitHub Wiki
Mid level cutscenes
User testing
The mid-level story cutscenes will be created using draft assets and then user testing will be carried out to determine whether users understood the story and what emotions the story evoked. The rough timeline for user testing the mid-level cutscenes is:
- 20th September - 1st October: Creation of draft story assets
- 2nd October: Draft story mid-level cutscenes are added to the game
- 3rd October: User testing of mid-level cutscenes
- 3rd October - 5th October: Implementing user feedback and finalising story.
For more details on the user testing, please see the story and NPC user testing wiki page.
NPCs
User testing
Draft assets and dialogue for each NPC will be added to the game and then user testing will be carried out to determine whether the user understood who/what each NPC is, and what emotions the user felt while interacting with them. The rough timeline for user testing the NPCs is:
- 20th September - 1st October: Creation of draft NPC assets
- 27th September - 2nd October: Draft NPCs are added to the game as they are complete
- 3rd October: User testing of NPCs
- 3rd October - 5th October: Implementing user feedback and finalising each NPC.
For more details on the user testing, please see the story and NPC user testing wiki page.
Unit testing
The NPC related classes contain unit tests for automated testing of the classes. The following unit test files have been created:
- FriendlyNPCAnimationControllerTest.java
- FriendlyNPCTriggerComponentTest.java
- FriendlyNPCFactoryTest.java
- SpeechIconComponentTest.java
Reflection on unit testing
Unit testing for the friendly NPC related classes have fairly extensive coverage as there were less UI elements involved in this sprint. As there were several dependencies, many classes needed to be instantiated or mocked to test the core aspects of the friendly NPC classes. This meant that the unit tests could fail due to a dependent class failing, which could be misleading. It is possible that the unit tests need to be refined more to lessen the impact from other classes; we will consider this for next sprint.