One of the most difficult situations for our testers is to accept bug report rejections by TLs. No matter how it feels, you need to understand that there are no personal reasons behind rejected bug reports. TLs review the bug report on the base of Test IO quality standards and makes the decision if it fits the standards or not. It doesn't mean that your testing capabilities are too low for us. In fact, we are giving you a chance to understand what went wrong with your bug report and how to avoid such cases in the future. That is why we have compiled the list of TL's rejection reasons with detailed explanations of what they mean and how to learn from them. You may find it in the table below.
How to improve?
Not a bug
This rejection reason means that you submitted a bug which appears to be normal feature behaviour.
Out of scope
This rejection reason means that you have submitted a bug which is valid but still not in the scope of the test.
This rejection reason means that you have submitted a bug that contains the same root cause as your fellow tester or a previously bug submitted by yourself and that your bug report was submitted after the original bug report.
The tip in this case would be to scroll down through the already submitted bugs before and after you submitted a bug, and check the features and titles first. If a bug looks like yours, you need to open it to see the description and check if the root of the problem is the same. If so, you must not submit a new report or delete your submitted report immediately. Keep in mind sometimes you might need to reproduce the bug by your fellow tester with an open console to understand if the bug cause is the same or not.
This rejection reason is used when your bug needs to be rejected because of a reason that is not a typical one.
The TL will always add some extra information explaining their decision, so you must read the rejection reason carefully to understand what is the issue with your report and how to avoid it next time.
This rejection reason means that the bug was already submitted in one of the previous test cycles and has been added to the list of Known Bugs. The customer is interested only in unique bugs that were not already reported by our testers in the previous test cycles.
This rejection reason means that your bug report quality is too low that we can't forward it to the customer in the state the way it is at the moment when TL reviews it.
The tip from our side would be to always double-check if you have listed all the required steps to reproduce the bug and to make sure that your bug report has a meaningful title and complete expected and actual results. If you are not a fluent English speaker, we suggest using Deepl to translate the text from your native language to English. Additionally, you can install the free Grammarly browser extension on your device and check the text for grammar before you submit the bug report.
Didn't follow instructions
This rejection reason means that you did not follow one or more instructions that were requested by the customer in the cycle instructions and features or requested by the TL via Chat, which caused you to submit a bug that break the rules and guidelines set by Test IO or the customer.
The tip in this case would be to always read the test instructions and the chat messages and ask your TL in the test cycle chat if something is not clear to you.
This rejection reason means that the bug you reported is caused by unusual user behaviour. In general, such bugs forced bugs are not interesting for our customers. Also, it means that the TL and other testers could not reproduce your bug using similar devices
This rejection reason means that the impact of the bug you found is not going to produce any significant inconvenience on the customer's side and that fixing it will produce too much cost than the benefits.
This rejection reason means that you have missed an opportunity to submit important additional information requested by TL which was necessary to reproduce the bug or to forward the bug with standard quality to the customer.
Low quality attachments
This rejection reason means that you have submitted a bug report with attachments which don't contain relevant mandatory information or the bug is not marked properly (in the case of Content and Visual bugs). It can also mean your attachments can't be opened in common browsers or their overall quality is not good enough and it's hard to see the problem.
This rejection reason means that your English or German language skills could be improved a bit in order to match our quality standards.
Wrong bug type
This rejection reason will be selected if the bug is valid and in scope, but you have selected the wrong bug type. For example: you submitted a VISUAL bug as a CONTENT one.