QA:Triage Policies and Procedures - Revision history

Sardisson: /* The very basics - queries, bugzilla search, etc. */ fix link, because apparently we renamed that

2011-01-11T06:11:48Z

The very basics - queries, bugzilla search, etc.: fix link, because apparently we renamed that

Sardisson: /* The very basics - queries, bugzilla search, etc. */ update for 2011

2011-01-11T05:56:23Z

The very basics - queries, bugzilla search, etc.: update for 2011

Sardisson: /* Common QA Troubleshooting Tips */ rewrite that for modernity

2011-01-11T05:54:23Z

Common QA Troubleshooting Tips: rewrite that for modernity

Sardisson: /* Using Talkback */ link to new Breakpad page; still need something about filing bugs based on breakpad

2009-10-05T23:12:21Z

Using Talkback: link to new Breakpad page; still need something about filing bugs based on breakpad

Sardisson: /* The very basics - queries, bugzilla search, ''etc.'' */ switch to Cm2.0 branch

2009-10-05T23:09:36Z

The very basics - queries, bugzilla search, ''etc.'': switch to Cm2.0 branch

Sardisson: /* Common QA Troubleshooting Tips */ add asking about inputmanagers and gecko1.9 profile-eating

2008-08-01T17:47:02Z

Common QA Troubleshooting Tips: add asking about inputmanagers and gecko1.9 profile-eating

Sardisson: /* Common QA Troubleshooting Tips */ add the AE logging stuff

2008-05-01T18:52:04Z

Common QA Troubleshooting Tips: add the AE logging stuff

Sardisson: /* Common QA Troubleshooting Tips */ add cookie logging

2007-11-10T07:50:38Z

Common QA Troubleshooting Tips: add cookie logging

Sardisson: /* Common QA Troubleshooting Tips */ some minor updating here

2007-08-15T03:54:13Z

Common QA Troubleshooting Tips: some minor updating here

Sardisson: /* Getting Started with Camino Bug Triage */ draftify

2007-06-30T04:09:31Z

Getting Started with Camino Bug Triage: draftify

@@ Line 4: / Line 4: @@
 ===The very basics - queries, bugzilla search, ''etc.''===
-Getting involved with Camino bug triage requires no prior skills, only a recent nightly build and the willingness to spend a little bit of time (as little as 5 minutes a day, 2-3 days a week).  If you're interested in helping out, please read this document (and ''[specify]'' some of the linked ones) and contact one of the leads or senior members of the [[Development:Project_Structure#Bug_Triage|Bug Triage team]] on [irc://irc.mozilla.org/#camino #camino on irc.mozilla.org].  While you don't have to participate on irc to do triage, it is ''helpful when starting out [tips]'' and always good to stop by at least occasionally to stay "in sync" with the rest of the team and the Camino project.
+Getting involved with Camino bug triage requires no prior skills, only a recent nightly build and the willingness to spend a little bit of time (as little as 5 minutes a day, 2-3 days a week).  If you're interested in helping out, please read this document (and ''[specify]'' some of the linked ones) and contact one of the leads or senior members of the [[Development:Project_Structure#QA & Bug Triage|Bug Triage team]] on [irc://irc.mozilla.org/#camino #camino on irc.mozilla.org].  While you don't have to participate on irc to do triage, it is ''helpful when starting out [tips]'' and always good to stop by at least occasionally to stay "in sync" with the rest of the team and the Camino project.
 Once you've done your reading and said hello, you're ready to jump right in.  At the most basic level, Camino bug triage involves weeding through all the bugs in the '''UNCONFIRMED''' state and either trying to reproduce the bug and get a clear set of steps required to do so, or finding a previously filed bug of which the new bug is a duplicate.  You should always test in a recent nightly build (no more than a week old), either from the <!--[http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-trunk/ -->trunk<!--]--> or, if there is ongoing development (often on a branch) towards a release, from the branch (for '''Camino 2.1''', that's the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-2.1-M1.9.2 Camino 2.1 nightlies]).  It's also helpful to have the latest stable release and corresponding Firefox versions on hand, but to start out, simply testing bugs in a recent nightly build is fine.

@@ Line 6: / Line 6: @@
 Getting involved with Camino bug triage requires no prior skills, only a recent nightly build and the willingness to spend a little bit of time (as little as 5 minutes a day, 2-3 days a week).  If you're interested in helping out, please read this document (and ''[specify]'' some of the linked ones) and contact one of the leads or senior members of the [[Development:Project_Structure#Bug_Triage|Bug Triage team]] on [irc://irc.mozilla.org/#camino #camino on irc.mozilla.org].  While you don't have to participate on irc to do triage, it is ''helpful when starting out [tips]'' and always good to stop by at least occasionally to stay "in sync" with the rest of the team and the Camino project.
-Once you've done your reading and said hello, you're ready to jump right in.  At the most basic level, Camino bug triage involves weeding through all the bugs in the '''UNCONFIRMED''' state and either trying to reproduce the bug and get a clear set of steps required to do so, or finding a previously filed bug of which the new bug is a duplicate.  You should always test in a recent nightly build (no more than a week old), either from the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-trunk/ trunk] or, if there is ongoing development on a branch towards a release, from the branch (for '''Camino 2.0''', that's the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-2.0-M1.9 Camino 2.0 branch]).  It's also helpful to have the latest stable release and corresponding Firefox versions on hand, but to start out, simply testing bugs in a recent nightly build is fine.
+Once you've done your reading and said hello, you're ready to jump right in.  At the most basic level, Camino bug triage involves weeding through all the bugs in the '''UNCONFIRMED''' state and either trying to reproduce the bug and get a clear set of steps required to do so, or finding a previously filed bug of which the new bug is a duplicate.  You should always test in a recent nightly build (no more than a week old), either from the <!--[http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-trunk/ -->trunk<!--]--> or, if there is ongoing development (often on a branch) towards a release, from the branch (for '''Camino 2.1''', that's the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-2.1-M1.9.2 Camino 2.1 nightlies]).  It's also helpful to have the latest stable release and corresponding Firefox versions on hand, but to start out, simply testing bugs in a recent nightly build is fine.
 ===QA Wanted===

@@ Line 30: / Line 30: @@
 == Common QA Troubleshooting Tips ==
 * [1:39pm] smorgan: We'll have to start being more diligent about asking about input managers<br>[1:39pm] smorgan: up front, that is<br>[1:39pm] smorgan: "I have problem x" "Do you have any input managers installed (e.g., 1Password)?"<br>[1:40pm] smorgan: Midly annoying, but probably necessary<br>[1:41pm] smorgan: We'll have to specifically mention 1Password, since people mostly don't know how it's implemented<br>
-* Be very careful asking people to test trunk/Gecko1.9 nightlies, since they do irreversible profile damage
+* It’s always useful to have users create a backup of their profile before testing something (since at various times Gecko changes will cause irreversible profile damage), or to have them use [http://pimpmycamino.com/parts/troubleshoot-camino Troubleshoot Camino].
 * [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 considered ignorable.
 * Clean profile/org.mozilla.camino.plist/check for haxies in (<code>~</code>)<code>/Library/InputManagers</code> and (<code>~</code>)<code>/Library/InputManagers/SIMBL</code>

@@ Line 143: / Line 143: @@
 Bugs resolved DUPLICATE, WORKSFORME, or INVALID '''are''' usually verified, but see above for a caveat when verifying bugs resolved WORKSFORME or INCOMPLETE through the “CLOSEME” system.
-== Using Talkback ==
+== Crash Report Analysis ==
 * Filing bugs based on topcrashers: [http://wiki.mozilla.org/Talkback_Topcrash_Analysis Talkback_Topcrash_Analysis]

@@ Line 6: / Line 6: @@
 Getting involved with Camino bug triage requires no prior skills, only a recent nightly build and the willingness to spend a little bit of time (as little as 5 minutes a day, 2-3 days a week).  If you're interested in helping out, please read this document (and ''[specify]'' some of the linked ones) and contact one of the leads or senior members of the [[Development:Project_Structure#Bug_Triage|Bug Triage team]] on [irc://irc.mozilla.org/#camino #camino on irc.mozilla.org].  While you don't have to participate on irc to do triage, it is ''helpful when starting out [tips]'' and always good to stop by at least occasionally to stay "in sync" with the rest of the team and the Camino project.
-Once you've done your reading and said hello, you're ready to jump right in.  At the most basic level, Camino bug triage involves weeding through all the bugs in the '''UNCONFIRMED''' state and either trying to reproduce the bug and get a clear set of steps required to do so, or finding a previously filed bug of which the new bug is a duplicate.  You should always test in a recent nightly build (no more than a week old), either from the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-trunk/ trunk] or, if there is ongoing development on a branch towards a release, from the branch (for '''Camino 1.6''', that's the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-1.6-M1.8 1.8 branch]).  It's also helpful to have the latest stable release and corresponding Firefox versions on hand, but to start out, simply testing bugs in a recent nightly build is fine.
+Once you've done your reading and said hello, you're ready to jump right in.  At the most basic level, Camino bug triage involves weeding through all the bugs in the '''UNCONFIRMED''' state and either trying to reproduce the bug and get a clear set of steps required to do so, or finding a previously filed bug of which the new bug is a duplicate.  You should always test in a recent nightly build (no more than a week old), either from the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-trunk/ trunk] or, if there is ongoing development on a branch towards a release, from the branch (for '''Camino 2.0''', that's the [http://ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest-2.0-M1.9 Camino 2.0 branch]).  It's also helpful to have the latest stable release and corresponding Firefox versions on hand, but to start out, simply testing bugs in a recent nightly build is fine.
 ===QA Wanted===

@@ Line 50: / Line 50: @@
 *** someone remind [[User:sardisson|sardisson]] to write AppleScript wrappers for these
 * http://kb.mozillazine.org/Standard_diagnostic_%28Firefox%29 (we need a Camino version; see [[User:Sardisson/To_Do]])
 * Blocked cookies (either too restrictive a global setting or some domain set to deny; many sites require cookies from multiple seemingly-unconnected domains in order to function).
 ** This is sometimes the case when something works in one browser but inexplicably doesn't work in Camino; users often have more restrictive cookie settings in their main browser but don't mess with the cookie prefs in alternate browsers.

@@ Line 40: / Line 40: @@
 *: <tt><nowiki>javascript:document.location.href%20=%20'http://webtools.mozilla.org/web-sniffer/?url='%20+%20escape(document.location.href) </nowiki></tt>
 ** [http://www.mozilla.org/projects/netlib/http/http-debugging.html NSPR http logging] for more complex cases
 * Random (but consistent) crashes, usually in Camino code (org.mozilla.camino or libobjc.dylib/system frameworks as the crashed thread):
 ** run with NSZombieEnabled (assumes Camino is installed in the standard location, and will eat lots of RAM and log to the console when you crash):
@@ Line 45: / Line 48: @@
 **: A more extensive version of the above, useful in some cases where the above is ineffective, is:
 **:: <code>MallocScribble=1 MallocPreScribble=1 MallocGuardEdges=1 NSZombieEnabled=YES /Applications/Camino.app/Contents/MacOS/Camino</code>
 * http://kb.mozillazine.org/Standard_diagnostic_%28Firefox%29 (we need a Camino version; see [[User:Sardisson/To_Do]])
 * Blocked cookies (either too restrictive a global setting or some domain set to deny; many sites require cookies from multiple seemingly-unconnected domains in order to function).

@@ Line 31: / Line 31: @@
 * [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 considered ignorable.
 * Clean profile/org.mozilla.camino.plist/check for haxies in (<code>~</code>)<code>/Library/InputManagers</code> and (<code>~</code>)<code>/Library/InputManagers/SIMBL</code>
 * Console.log
 * http headers (browser and server)
@@ Line 46: / Line 49: @@
 ** This is sometimes the case when something works in one browser but inexplicably doesn't work in Camino; users often have more restrictive cookie settings in their main browser but don't mess with the cookie prefs in alternate browsers.
 * Move UA spoofing from hidden prefs to this page, to make it clear that it's a QA tool, not something we "endorse" for everyday use like other hidden prefs.  If people are smart enough to find the instructions themselves, we're going to hope they're smart enough to use it responsibly.....
 * [11:40pm] smorgan: Someone should make CaminoConflictCatcher <br>[11:41pm] ardissone|in: lol <br>[11:41pm] smorgan: Copies the profile to a temp location, launches there, and removes prefs.js lines one by one, relaunching each time<br>[11:41pm] smorgan: And it pops up a box when you quit: "Was the bug still there?"<br>[11:41pm] smorgan: And then tells you what line it last removed when it said no<br>[11:41pm] smorgan: That would be awesome<br>[11:42pm] ardissone|in: sounds like a job for Wevah Wonka's Cocoa Factory<br>[11:42pm] ardissone|in: or Froodian's Camino Therapy Couch<br>

← Older revision		Revision as of 04:09, 30 June 2007
Line 1:		Line 1:
		+	{{draft}}
	== Getting Started with Camino Bug Triage ==		== Getting Started with Camino Bug Triage ==