QA:Home Page
Contains information on Camino's quality assurance procedures, including triaging bugs and testing the Camino application itself.
Bug Triage
QA:Triage Policies and Procedures explains how the triage team goes about its daily work and how it interacts with the larger Mozilla.org triage community. This page also explains how to get started with the Camino Bug Triage team.
QA:Bugzilla:Searching For Dupes contains information on how to search Bugzilla for duplicates prior to filing. This information will join the Bugzilla FAQ bug exists here for previewing and discussion.
- Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.) Some of the information developed in this document, however, is intended primarily for triage team members and will likely end up elsewhere (not /support/) on cb.o
QA:Keywords & Status Whiteboard explains some of the commonly-used keywords and status whiteboard entries.
QA:Hardware Configurations is a mostly-complete list of hardware available to each QA or developer, useful when seeking patch testing or triage in a certain configuration.
QA:Bugzilla:FAQ contains the most recent version of our Bugzilla FAQ. This wikified version is the pre-cb.o version to allow discussion of the proposed changes. (See User:Sardisson/To_Do for some initial thoughts on things to add.)
- Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.)
- "Also, if you have debugging information that is more than 20 lines long, it should be an attachment rather than pasted into the Additional information." [1]
- See also the AbiWord Bug FAQ; we should incorporate some of these items.
- Samples of good initial bug reports: [2]
- See also the AbiWord Bug FAQ; we should incorporate some of these items.
- "Also, if you have debugging information that is more than 20 lines long, it should be an attachment rather than pasted into the Additional information." [1]
Release Testing
QA:Release Testing describes the smoketests that should be performed on release candidate builds to make sure everything is functional before releasing (coming soon).
Other
QA:Mac 101 lists answers to common questions that really shouldn't have to be answered by Camino support/QA but nonetheless are asked too often.... Add your good "stock answers" here.
QA:Damaged Bookmarks provides instructions on reporting data from bookmarks corruption logging.
This page has been protected from editing.
