865
edits
QA/TDAI/RegressionRangeFinder: Difference between revisions
no edit summary
No edit summary |
|||
| Line 3: | Line 3: | ||
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:<pre>python regression.py -g 2009-02-03</pre> | 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:<pre>python regression.py -g 2009-02-03</pre> | ||
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 the bug is present in that build | 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 the bug is present in that build. | ||
After you've tried enough builds (about 7 for a 100-day initial regression range), you'll see something like this: | After you've tried enough builds (about 7 for a 100-day initial regression range), you'll see something like this: | ||