Long Term Bug Reporting
Introduction: Provide beta testers a way to quickly report urgent bugs to your development team. Speed up the final testing stages by enabling direct communication between developers and users - providing a structured system within which critical issues can be highlighted.
Method: Invite trusted beta testers to complete web based report cards for every bug they encounter. It should be clear to participants that one report card should be filled out per bug, as this will ensure feedback remains focused and the root of each issue can be found easier.
Long Term Bug Report Cards
Encourage beta testers to write a description of how the bug was triggered, explaining the events immediately preceeding it and the effect of the bug. Understanding the full scenario will give developers the best possible chance at replicating and resolving the issue. Also, ask for screenshots to be included where possible to highlight where the problem was found or showcase the effects it had.
Finally, participants should also rate the bug on a scale of 1 - 10 that indicates how detrimental it was to their web browsing experience. A score of 1 indicates that while something went wrong, it did not have any real impact. A score of 10, on the other hand, would indicate that the bug was so severe it stopped the user from proceeding.
Benefit: Utilise participant feedback to elimate as many bugs as possible before a full scale launch. The earlier these issues are noticed, the less likely they are to cause problems after your site has been publicly released. The direct nature of report cards facilitates a straightfoward reporting process, streamlining how bugs are found and resolved.
Complement long-term bug reports with a User Acceptance Testing forum in which beta testers can discuss and elaborate on potential issues.