QA:Triage Policies and Procedures
Jump to navigation
Jump to search
Contents
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
Searching for Duplicate Bugs
Moving Bugs to Other Products and Components
- 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
Regression Windows
- Old nightlies on ftp.m.o
- Older nightlies on archive.m.o
“CLOSEME”
- Dealing with old UNCOs
General Mozilla Policies
- links to QA docs, bugzilla etiquette
- http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html (ask pink for privs in Camino; exisiting QA will vet you)
- https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
- https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html
