-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 3 User Testing Basic Attack (team 1)
In this sprint, since no team is currently responsible for making an attack function, we are also responsible for making a simple attack function in this sprint so that players can have basic interaction with the enemy.
Therefore, this test is mainly used as the initial test of the attack function. By testing the initial attack function, we will have the opportunity to obtain a lot of improvement suggestions, and consider further improving it in the subsequent development.
This test mainly focuses on testing the attack function, this will be measured by user satisfaction and opinions.
Show the user directly how our attack function performs in the game. (In order to allow users to evaluate our existing attack functions more intuitively)
Collect feedback via questionnaire form and interview
The participants in this test are mainly from other classmates and acquaintances, as well as some other members of the same studio. Additionally, all tests are online via zoom due to the conditions required for the test. A total of 10 people participated in the test.
Overall, the process went according to plan, first we directly showed the user how the existing attack functions performed in the game, after the demo, a questionnaire is provided to the user. After the questionnaire is submitted, we conduct another interview with the user for further feedback.
The link of questionnaire: https://forms.gle/fwMqKm8G6SXyJsht8
Most of the feedback received so far is between moderate or good evaluations, and combined with the improvement suggestions in Q2, it can be found that although the existing attack functions are reasonable as basic attack functions, most users still expect to add more attack methods in the follow-up work to enrich the gameplay.
Overall, this user test provided a good start to our attack functionality, and it gave us further development direction.
Based on the information gathered in this sprint, we can plan some features that may need to be tested in the next sprint, including:
- Richer attack methods
- If possible, add certain strike effects, such as popping up damage numbers when attacking, to make the game more "juicy"
Therefore, maintaining communication with other teams is still necessary, and the difficulty of each task should be assessed in a timely manner to ensure the progress of the work
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack