HOW TO AVOID DUPLICATE REPORTS

 

This time we will cover the elephant in the room. The king of rejection, duplicate reports.

 

This may seem obvious at first but it is still a mistake made often. In fact, this rejection reason occurs twice as often as any other rejection reason.

When reporting an issue, if the same issue has already been reported, it will not be considered valid.  

 

 

Here are some steps you can take to ensure the issue you report will not get rejected.

 

  • First most important step: Read the tester spec carefully. There are certain types of issues that are considered duplicates as long as the method of causing the issue to occur is identical, even if they occur in different areas of the application. If you find a behavior that has already been reported, it is best to comment on an already reported issue and mention any other areas where this occurs, even if the issue does not belong to you.

 

  • Second crucial step: Check the known issues list. Many projects will often have a list of issues previously reported that are known and have not yet been addressed. Check the Tester Spec document to see if a known issues list is present before starting to test.

 

  • Third key step: Check the issues reported on the cycle.  Hop into the tracker and see which issues were already reported. Many of the issues encountered will generally occur on multiple devices. The easier it is to find and replicate the issue, the higher the chance this was already discovered and reported. Note that rushing is not ideal, not only will your issue be rejected, but you will have spent time reporting an invalid issue which could have otherwise be spent checking for other issues.

 

 

 

Please note that in the future, moderation will be stricter which means reporting inappropriate or incomplete issues will have weight on your standing. The less efficient the testing is, the less likely it will be for you to join additional cycles later down the line. Strive to be the best you can be!

 

I hope you found this email informative. We want this newsletter to be valuable to you so please share your feedback. In the next newsletter, we will dive into the second-most common rejection reason “Not an Issue”.

Copyright 2017 © Tester Work and Global App Testing