QA:Triage Policies and Procedures

Common QA Troubleshooting Tips

[01:06am] smorgan: Clean profile is supposed to be a narrowing down tool, not a magical remover of bugs. Only corrupt/invalid profiles that appear to be caused by users mucking around should be consider ignorable.
http headers (browser and server)
http://kb.mozillazine.org/Standard_diagnostic_%28Firefox%29 (we need a Camino version; see User:Sardisson/To_Do

Don't confirm RFEs (bugs with severity set to enhancement, or enhancement requests misfiled with some other sort of bug severity, which are very common, particularly if another browser provides such a feature) until there has been discussion among the triage team and, in some cases, with the project lead(s). This helps combat feature creep and keeps Camino from having a kitchen sink.

Don't confirm any bug that looks like it has the potential of being a Core bug (anything that has to do with the content area, or with certain app features whose underlying implementation is tightly linked with the Core, e.g. the pop-up blocker, session or global history); see Moving Bugs to Other Products and Components below for more about moving bugs to Core components.

Don't confirm bugs that look like they might be resolved DUPLICATE, INVALID, or WONTFIX. Perform a search of old Camino bugs with these resolutions before confirming bugs (especially the latter two; a request or bug may have been WONTFIXed before you began QA work, but that doesn't mean the project lead(s) have changed their opinion. See QA:Bugzilla:Searching For Dupes for more on search for duplicates, including duplicates of WONTFIXed and INVALID bugs.

If the bug has a clean report and is clearly a real bug in the Camino application UI, then by all means confirm the bug. Otherwise, proceed more cautiously, seek additional opinions, etc., before confirming a bug.

When to set priority and target milestone; fixing other fields (Camino component, QA, branch)...

assignee
status (UNCO vs. NEW; what's required)
testcases (esp. for layout and printing; link to bugathon doc)
moving to TE (TE summary format)
Core:Needs Triage
Setting and Using Flags
Setting Milestone, Priority, and Severity [link to bugzilla page on severity]
Adding keywords and status whiteboard info
http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html covers a lot of this