Dadas

Become a Game Tester now! Yes, as you read, this game is created with the aim of finding BUGs and reporting them! Dadas, it is a Beta game, intentionally created by me with visible but also hidden errors. There are 5 Levels in total, but your testing starts from the beginning of the menu. The good part is, if you don't want to test, you can simply play and at the end share your score with other players!
As a game tester, your main job is to test the Dadas game and identify any errors, bugs or problems that may occur during gameplay. Here are some steps and tips on how to be an effective game tester:
1. Start with a deep understanding of the game concept: Read and understand the game documentation, including the story, game features, objectives and game mechanics. The more familiar you are with the game, the easier it will be to spot issues and provide relevant feedback.
2. Try to find bugs and problems: Explore as many areas of the game as possible and interact with all possible elements to discover bugs or problems. Be on the lookout for programming errors, inconsistent graphics, strange animations, no sound, or anything else that might indicate a problem with the game.
3. Document your observations: As you playtest, document all of your observations. Write down the bugs you find, describe how they were generated, and record the step-by-step procedure to reproduce the problem. It also includes details such as the configuration of the system used and any other relevant information.
4. Be creative and a critical thinker: Try to break out of patterns and try combinations of actions or unusual scenarios that might lead to errors or abnormal behavior. Think outside the box and pay attention to details that others might overlook.
5. All BUGs are sent to the email address: dadasbugs@gmail.com
It can be sent directly in writing or in docx, xlsx format!
Attention! Do not report more than one error in a report. For each BUG, ​​a separate report must be written
Be clear and constructive
These steps are for reporting a bug!
The report contains:
1. Issue Title or short Description
2. Type:
- Happy
- Performance
- Visually
- Functional
- Crash
3. Frequency:
- Every time
- Occasionally
- Once
4. Priority:
- Low
- Medium
- High
- Critic
5. Steps for reproduction
6. Expected result
7. The actual result
8. My Environment
9. Attachments