QA/TDAI/RegressionRangeFinder: Difference between revisions
| Line 11: | Line 11: | ||
=Other features= | =Other features= | ||
Mozregression has a few command line options: | Mozregression has a few command line options: | ||
*<tt>-h, --help</tt> | *<tt>-h, --help</tt><span style="margin-left: 30px;">show the help message</span> | ||
*<tt>-b YYYY-MM-DD, --bad=YYYY-MM-DD</tt> | *<tt>-b YYYY-MM-DD, --bad=YYYY-MM-DD</tt><span style="margin-left: 30px;">first known bad nightly build, default is today</span> | ||
*<tt>-g YYYY-MM-DD, --good=YYYY-MM-DD</tt> last known good nightly build | *<tt>-g YYYY-MM-DD, --good=YYYY-MM-DD</tt><span style="margin-left: 30px;">last known good nightly build</span> | ||
*<tt>-e PATH1,PATH2, --extensions=PATH1,PATH2</tt> list of extensions to install (absolute or relative paths) | *<tt>-e PATH1,PATH2, --extensions=PATH1,PATH2</tt><span style="margin-left: 30px;">list of extensions to install (absolute or relative paths)</span> | ||
*<tt>-p PATH, --profile=PATH</tt> | *<tt>-p PATH, --profile=PATH</tt> <span style="margin-left: 30px;">profile to use with nightlies (absolute path)</span< | ||
*<tt>-a ARG1,ARG2, --args=ARG1,ARG2</tt> command-line arguments to pass to Firefox | *<tt>-a ARG1,ARG2, --args=ARG1,ARG2</tt><span style="margin-left: 30px;">command-line arguments to pass to Firefox</span> | ||
Revision as of 21:52, 31 March 2010
Mozregression is a python command-line tool for finding a bug's regression range on Firefox nightly builds. Use the installation instructions for your platform. As an example, if you know a bug wasn't present in the nightly for Feb 3 2009, but is present in today's nightly, you can run this command-line:
python regression.py -g 2009-02-03
This will download and run a series of nightly builds on a new, clean profile. When a new browser window pops up you can do whatever you need to do to verify the bugs presence in that build, then type 'good' or 'bad' into the prompt depending on whether that nightly is good (bug isn't present) or bad (bug is present), the program will keep on downloading builds depending on your answers. After you've tried enough builds (about 7 for a 100-day initial regression range), you'll see something like this:
Last good nightly: 2009-12-22 First bad nightly: 2009-12-23 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1f0e04dc2b21&tochange=f8b8f2f214d6
this is good information to paste into a Bugzilla comment. The pushlog url will show you all the code checkins that occurred during the regression range.
Other features
Mozregression has a few command line options:
- -h, --helpshow the help message
- -b YYYY-MM-DD, --bad=YYYY-MM-DDfirst known bad nightly build, default is today
- -g YYYY-MM-DD, --good=YYYY-MM-DDlast known good nightly build
- -e PATH1,PATH2, --extensions=PATH1,PATH2list of extensions to install (absolute or relative paths)
- -p PATH, --profile=PATH profile to use with nightlies (absolute path)</span<
- -a ARG1,ARG2, --args=ARG1,ARG2command-line arguments to pass to Firefox