Heya! My name is Juan (@JuanGamerPlayz_RBLX) and I am also associated with experiences that @Abcreator QA tests as well such as “Rainbow Friends”, a popular experience since 2021 with the variety of more than 10-20K DAU (Daily Active Users).
Reviewing the topic and every chapter, led me to also contribute by providing further information about the importance of applying QA (abbreviation of Quality Assurance).
Summary:
-
Bugs
-
Feedback
> Bugs
Methods to Locate Bugs:
While having an active testing session hosted by developers and/or contributors of the following experience you are QA testing, sometimes, we do not know where to begin with… “What do I report?”, “Do I follow the others near me?”. Many questions can come up to our minds and interrupt us from thinking. It is recommended to stay calm and begin by producing a simple analysis of the experience information, the title, description, etc.
Let’s see using the experience of “Natural Disaster Survival” as a short example:
It is always good to report the information in cases of having multiple sentences and/or paragraphs censored, which can make up players unable to comprehend what is the objective in-game as a summary:
Badges and Gamepasses are as well good to always be sure that they are capable to see overall.
The next step is to join the Roblox experience and test how the visual interfaces work and if you can communicate with them one by one. We can also communicate with in-game events and look forward to their respective results as expected. However, it is primary to note that you can choose which of these you would like to start. Every tester has their perspectives and cases to identify… Therefore, do not copy their ways, be creative!
Creating a Bug Report:
Whenever encountering a bug you have found, it is always good to note them, state how are their impact from low (does not damage too much the experience) → critical (does damage the experience highly) and reproduce the steps for the developers understand where and how to showcase the issue. It does not need to be long and filled with basic details, you can make it short as long as it is following the context and is easy to get it right away.
» Here is a demonstration and let’s apply the experience of “Natural Disaster Survival” as the sample for this area:
Juan’s Bug Report:
- In the Happy Home map, the house does not fall apart during a round of disaster called “Earthquake”;
- In the lobby, the billboard advertising the green balloon does not provide any information to buy the game pass.
Images and videos are also good guidance for them to see in real-time how the player saw. If the place allows you to submit files, then it is your chance to provide them right in time!
> Feedback
Structuring your Feedback:
Quality Assurance not only tests the quality of the product but can also deliver feedback! Feedback helps to indicate how the product can be better in the context of the overall perspective of regular users while experimenting, UX (abbreviation of User Experience).
Structuring your feedback needs to first apply the simple basis, which we can begin by asking ourselves: “Why the experience was difficult for me?”, “Could it be complicated for the rest?”… It is good to remember the steps you have passed along the way and reflect on how complex it was to get to think how other regular and new players experience the same action. Always good to think of others that are newbies and tell them what can be good for them such as tutorials at the beginning, advice in-game, and so on.
» Let’s think of NDS, its objective, and how players can comprehend great joining and walking by:
Feedback Report:
- Provide a tutorial that explains what are the perks of buying the green balloon in Natural Disaster Survival;
- Every disaster should have an explanation about them and how to survive shortly.
Again, every tester has their ways to do so and you should always be unique while still following the content.
Feedback and Recommendations:
The very last topic to mention within this chapter is regarding feedback and recommendations.
Sometimes, when we come up with these, we usually confuse them as considering both of them the same but as synonyms… This is fine, yet it can be bad on the other side as the developers may see it differently and not take it into further consideration.
Feedback → information available by a person once reacting to a product and suggesting improvements.
Recommendation/Advice → A recommendation from something or someone to use because it is good for the best practices.
Difference → Feedback is either a reaction/response to a particular process or activity while for Advice, opinion, or recommendations offered as a guide to action, conduct, etc.
Having the knowledge about both of them and getting that all aren’t similar or equal, you may apply them separately as the developers analyze, review everything, and pick by part those that are primary and can genuinely contribute to a better experience for players!
And that is about it! Hopefully, my reply was also helpful and could assist with the topic of this tutorial.
I wish you all amazing luck and lets QA! 