If you find a bug but it has already been reported by another tester, you unfortunately may not submit the same bug again, but what you can do is to submit a reproduction! Reproductions are useful for customers because they indicate which environments are concerned and if the problem is device-specific or not. Hence, it gives customers a better idea how severe the bug is. 

To reproduce a bug, follow the same steps as described by the original tester in his/her report. If you experience the same bug as the original tester, we call that a positive reproduction. If you cannot reproduce the bug despite following the same steps, we call it a negative reproduction.

A negative reproduction should show that the function works on your device, so that you don't experience any bug. If you experience a different bug, you should instead submit a bug report or reproduce another tester's bug report who submitted that problem.


Rules

Attachments for reproductions should only show the most necessary information: 

  • If you can show the bug with a screenshot, attach a screenshot only.
  • If you really need a screencast to show the bug, f.i. when an action is required to trigger the bug, upload a screencast.
  • In most cases, showing the triggering action and the bug is enough.
  • The reproduction screencast should not be longer than 10 seconds. If you can’t show all necessary steps within 10 seconds, e.g. when showing a loading process, your screencast can be longer but never longer than 1 minute.

Reproduction screencasts are not allowed to be longer than the screencast from the original report. Reproductions which don’t comply with the rules will be rejected. Examples: If you submit a screencast instead of a screenshot, if the screencast is too long, or if the screencast shows unnecessary steps.

Reproducing content problems is not allowed. This includes content problems that are submitted as functional bugs, e.g. linking problems in the navigation menu, header, or footer of websites.

As for bug attachments, you need to show the date on your attachment.

When reproducing an app crash, upload a crash log file in addition to your reproduction screencast. The screencast that documents the crash has to correspond to the attached crash log, i.e. timings must be coherent. 

If you reproduce an invalid bug (e.g. wrong environment selected or with wrong device setup), your reproduction will be rejected.


You can only submit a reproduction for a bug if:

  • the test is currently running
  • it is not your own bug
  • it is a functional report
  • the report is not rejected and not accepted by the customer
  • you have a required device (see right sidebar on test overview page)
  • you haven't submitted a reproduction for it yet
  • it has not already been reproduced with your device(s) by other testers
  • the maximum number of reproductions for each bug report in this test has not been reached (depends on the customer's purchased plan)

In all other cases, you will not see the “Can you reproduce this bug: Yes or No” button in the bug report view. If you see that button, you are allowed to submit a reproduction.


Related articles:

Did this answer your question?