At Testlio, reporting a duplicate issue is considered unprofessional. The tester should always check in the issue-reporting section whether the issue is already reported to avoid unnecessary “noise” to Test Leads, Project Managers, and especially for the clients, during a test cycle. Never report a duplicate issue, unless you have been told otherwise, because this may also negatively impact your tester’s score.

When should you consider an issue as a duplicate?

It is all about the root cause - Identifying a duplicate comes down to whether the original issue has the same root cause as the one you found. If so, then the issue you’ve found is a duplicate and it doesn’t matter whether you have a different device or OS version from the original issue it was reported with. 

Different flows but same issues - Sometimes it is possible that the same issue can be found by taking different flows but the outcome is an issue that has already been reported. Again, it is considered as a duplicate. 

Closed issues - Whether or not to report already closed issues varies between projects. Sometimes, when you do come across an issue that has already been closed, then we recommend to always check the reason why it has been closed. If the reason is mentioned as “too minor” or “won’t fix” then you should not report this as an issue. But when the severity of the closed issue is marked as “high” and also labeled as “fixed” but you still managed to find the issue, then you can report it in the correct way by creating a new one.

A little reminder to every tester

We do encourage you to concentrate on testing and not just on finding bugs. People tend to think that if you’ve only found one bug then you haven’t done your job well. This is not the case with Testlio. Let’s not forget that we value the quality versus quantity approach to QA app testing compared to other crowd-sourced testing platforms.

How to search for duplicates on Testlio platform

If you haven’t checked how to look for duplicates on the Testlio platform yet, you can watch a video and read some additional notes from here.

Did this answer your question?