Have you ever played this awesome game where a guy in a green tunic travels around a kingdom called Guyrule (Not actual name) with this amazing blue shield and sword? I did! Did you ever come across this one problem in said game where you would go talk to a specific character that would give you a set of 3 missions. If you followed the list in order and returned to that same character, your game data would be corrupted, making that 5 hours of re-spawning game play go down the drain.
Oh hoho, I did and let me tell you I wasn’t too pleased with the creators. But why would I bring an issue you may or may not have heard of? Well, dear children of Eggverse, you may have encountered a issue similar in another game. Maybe something that was clearly broken, awfully implemented or even upsetting to play?
So now I ask you this important question. If you found an issue like the one I just described, how would YOU go about reporting the issue to the creators of the game? That’s where writing a bug up comes in. As QA testers, we are tasked with finding and writing up every issue we can find in a game in order to help developers. This helps them make the necessary fixes or changes so the game doesn’t break or look bad. QA needs to find, locate, and instruct the programmers on how to find the issue on their own while we continue to find more bugs. We are like mission control, we give out the coordinates and the programmers go out and diffuse the bomb. If the code a programmer wrote does not work as intended, we send back the issue in order for them to work on another fix.
Now writing up a bug may sound like the simplest thing to you. Total walk in the park right? Alright, let me test you on your assumption. In 8 steps, could you walk me through how to make a peanut butter and jelly sandwich? Is your first step to go buy the ingredients or take the bread out? Wrong! (There’s the door, see yourself out)
You see, you already have all the supplies in front of you. Why would you waste a step on telling someone who already has the set up to make this delicious PB and J sandwich to go buy bread?
Each and every issue that we write into our database consists of 3 major things.
* Steps to Reproduce
All three are important. What is most important is to write a clear and detailed report on what it is that was found. We write up issues with the most detailed amount of steps and information to help our programmers resolve the issue that we encounter. And sometimes we add a picture of the issue for good measure. (That’s because QA doesn’t want to come off as crazy liars when the programmers can’t reproduce the issue. We have PROOF, we tell you! PROOF!) We do it to not only help them out, but also so when we go back in to check if the issue is fixed we aren’t confused on what our team member found.
So you can bet that when a bug like “A crashed occurred when tapping a button in room” is submitted it drives QA bonkers. Like, what room where you in? Which button did you push? What were you doing before you went into the room? Is it a soft crash or a hard crash? Did it delete your file? Did this happen before or after you got the Hylian Shield because if it happen after, you just spent 5 whole hours of boss battles for nothing! NOTHING! (Sorry, it gets me every time)
Details! It’s all about the details. You wouldn’t tell a cop that someone stole your awesome PB and J sandwich without telling them it was a large purple dinosaur with some whiter than white teeth and green spots on its back. How would justice be served!? Justice, to that beautifully made PB and J!
So remember kids, when reporting an issue, it’s always important to spread the peanut butter before the jelly. OH! And the details, the details are also important.