“In a new test of the same customer, you must NOT resubmit more than 5 old, still occuring bugs.”
“Don't check old tests; Just start testing the environment test with fresh eyes.”
Finding new bugs can be hard – We know! You might instead find yourself retesting bugs from previous tests and submitting them again if they still occur. Even though it is not forbidden to copy bugs on the platform, certain rules come into play regarding copying your own bugs or reports from other testers.
Note: Your focus on the platform should be finding new issues instead of reporting the same bugs again. We do not allow massive copy-pasting of bugs.
What does "Massively" mean?
If you participate in test A where you reported more than 5 bugs, you might get invited to join test B for the same customer product. According to the rules mentioned in the Recurring Tests article, you are – in some cases – allowed to submit those bugs again.
In a new test of the same customer, you must NOT resubmit more than 5 old, still occuring bugs.
Otherwise, it will be considered massively copy-pasting bugs, which can lead to a warning or a permanent ban.
Avoid this trap like this: Don't check old tests; Just start testing the environment with fresh eyes.
Rules and Ethics
You don't have any copyright on a bug when you submit it to the platform; You don't own it.
Reporting old bugs in a new test again is not providing additional value for us or the customer. Focus on finding new issues, not copying old reports. Such behavior may lead to a warning or to a permanent ban in extreme cases.
When you copy a bug report, you must NOT change anything its details. There is no reason to change Title, Steps, or Results. You are only allowed to change:
the attachment that must be recorded newly
used credentials (if any)