QA/Community/QMO Design/External Docs/other: Difference between revisions
< QA | Community | QMO Design | External Docs
Jump to navigation
Jump to search
No edit summary |
Samuelsidler (talk | contribs) No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<small>[[QA/Community/QMO Design|« QA/Community/QMO Design]]</small> | |||
== QA tools and apps == | == QA tools and apps == | ||
* http://reporter.mozilla.org/app/ (Broken website reporter) | * http://reporter.mozilla.org/app/ (Broken website reporter) | ||
| Line 25: | Line 27: | ||
* http://www.squarefree.com/2006/11/02/determining-whether-a-crash-looks-exploitable/ (How to report a crash on Firefox) | * 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) | * http://www.google.com/calendar/embed?src=m42o9ivukgvpn17bvalf4iv0mk%40group.calendar.google.com (MozQA group calendar - maintained by timr) | ||
* http://dmoz.org/Computers/Software/Software_Engineering/Quality_Assurance/ (search results for quality assurance might help us find some good stuff) | |||
* http://www.ifolder.com/index.php/Testing (for ideas on how to break down QA focus areas) | |||
* http://www.reservesdirect.org/wiki/index.php/QA_guide (for ideas on writing a general qa guide) | |||
* http://headrush.typepad.com/creating_passionate_users/2006/12/how_to_build_a_.html (how to create a user community, something everyone should read if they are going to be involved in QMO). | |||
== Social Networks == | |||
* StumbleUpon (http://www.stumbleupon.com/tag/qa/, http://www.stumbleupon.com/tag/quality-assurance/) | |||
[[ | <small>[[QA/Community/QMO Design|« QA/Community/QMO Design]]</small> | ||
Latest revision as of 05:17, 15 November 2007
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)
- http://dmoz.org/Computers/Software/Software_Engineering/Quality_Assurance/ (search results for quality assurance might help us find some good stuff)
- http://www.ifolder.com/index.php/Testing (for ideas on how to break down QA focus areas)
- http://www.reservesdirect.org/wiki/index.php/QA_guide (for ideas on writing a general qa guide)
- http://headrush.typepad.com/creating_passionate_users/2006/12/how_to_build_a_.html (how to create a user community, something everyone should read if they are going to be involved in QMO).