QA/Community/QMO Design/External Docs/other

QA tools and apps

• http://reporter.mozilla.org/app/ (Broken website reporter)
• http://talkback.mozilla.org (Talkback crash analysis)
• http://hendrix.mozilla.org (Mozilla feedback system)
• http://bugzilla.mozilla.org (Bugzilla bug tracker)
• http://litmus.mozilla.org (Mozilla test tracker)
• http://tinderbox.mozilla.org (Build status)
• http://bonsai.mozilla.org (Checkins status)
• http://mxr.mozilla.org (Mozilla code cross-reference)

MDC (developer.mozilla.org)

• http://developer.mozilla.org/en/docs/Bug_Writing_Guidelines (Easy to follow guidelines to make effective bug reports, could link to in a testing FAQ)
• http://developer.mozilla.org/en/docs/Category:Automated_testing (Developing automated tests)
• http://developer.mozilla.org/en/docs/Category:Automated_testing (List of ways to test software updates)

mozillaZine

• http://kb.mozillazine.org/Knowledge_Base (Knowledge Base)
• http://forums.mozillazine.org/ (Forums)
• http://weblogs.mozillazine.org/qa/ (soon to be old QA Blog)

Useful QA Pages

• http://wiki.flock.com/index.php?title=Verifying_a_bug (needs to be updated to reflect Mozilla community, contributed/maintained by Eli Goldberg)
• http://www.gerv.net/hacking/before-you-mail-gerv.html (need to convert it to before mailing qa doc)
• http://bcheck.scanit.be/bcheck/ (Browser security test site)
• http://www.squarefree.com/2006/11/02/determining-whether-a-crash-looks-exploitable/ (How to report a crash on Firefox)
• http://www.google.com/calendar/embed?src=m42o9ivukgvpn17bvalf4iv0mk%40group.calendar.google.com (MozQA group calendar - maintained by timr)

Back to QMO Design