I’m always filing bugs, and I usually know the Bugzilla component they’re supposed to go in. So I made a shortcut to get around the hoops of picking a component on the Bugzilla form. It’ll autocomplete on product and component name for faster filing:
I also often search for bugs by summary in a component, so I made a shortcut for that too. You can search for open, closed, or both:
I’m interested in the common fields other people use when searching for bugs, so if you have any insight leave a comment.
Nightly Tester Tools is an addon for Firefox nightly and beta testers. I’m the current maintainer of the addon, having been passed down the torch by Dave Townsend. It’s at the point where I no longer have time to give Nightly Tester Tools the attention it deserves.
Nightly Tester Tools has been around for a long time. It’s provided tools like build id copying, screenshots, and test crashing. The code is currently on Github, and there’s a Bugzilla component Other Applications/Nightly Tester Tools Where people file bugs.
Maintenance mainly involves bumping the version compatiblity on AMO every time there’s a new Firefox release and checking out new bugs or feature requests that come in.
This is a great opportunity for a nightly tester to build onto a tool that helps out thousands (NTT has about 100,000 users) of testers, and learn some extension development at the same time.
Please get in touch if you’re interested. I’m harth on #ateam on irc.mozilla.org and always available to answer questions about it and guide anyone along about the process.
Nightly Tester Tools 3.0 has been released, containing some new features. Among the added features are Crashme functionality, copying about:support to pastebin, and viewing the pushlog of changes since the last nightly.
Since the update about the future of Nightly Tester Tools, there’s been some discussion around the addon compatibility feature. We decided to take out addon compatibility fixing for individual addons, but left in a checkbox that overrides compatibility checking for all addons. It works in the same way Addon Compatibility Reporter does, but everyone’s encouraged to install ACR to help report compatibility issues to addon authors.
Aakash has been working on a mobile version of NTT, with a few of of the same features of the desktop version and a few mobile-specific ones. Nightly Tester Tools 3.0 for mobile has also been released.
You can request a feature by filing an NTT bug. Check out the code on Github (mobile code here).
Some of you may have noticed that the aptly named Nightly Tester Tools addon doesn’t work on nightly builds at the moment. A few months ago Dave Townsend mentioned that the popular Nightly Tester Tools extension was in need of some new owners and an update. A couple of people that work on automation have decided to lead an effort to revive Nightly Tester Tools and make it even better.
You can check out the list of current and proposed features on the wiki. We’re planning on removing a couple features, some of which have been superseded by Firefox features, including: crash report sidebar, session restore, and leak log analysis. Let us know if you use any of these features. In addition, we’re thinking about taking out the extension compatibility fixing. Extension compatibility is the main(/only) reason many people use Nightly Tester Tools, but now there’s the Addon Compatibility Reporter that keeps up to date with the extension compatibility changes (EDIT: many people have protested this and given some good reasoning, so it’s likely this will stay in).
A couple people already working on the effort are harth, jhammel, and aakashd on #qa on irc.mozilla.org. If you have any features you’d like to see in NTT you can of course comment on this blog post, or file a bug in the Nightly Tester Tools component.
If you’d like to contribute code, fork the Github repo. We’re sticking with the old code base for now but are keeping an eye on the Jetpack SDK for a switch at some point.
A good while ago I made a regression range finder for Firefox nightlies. It was a Python script intended to make it easier for people to manually find the regression ranges of bugs on the nightlies. The other day, someone actually used it! So I decided to revisit it and fix it up and make it easier to install. There’s more info about it here, but here’s a quick summary:
install with setuptools or pip if you know how to do that, otherwise checkout out the OS-specific installation instructions
run on the command line:
mozregression --good=2010-03-19 --bad=2010-09-12
Several nightlies will be downloaded and automatically run for you, asking you to check for the existence of the bug in each one, ending up with something like:
Last good nightly: 2010-09-08 First bad nightly: 2010-09-09
if you have questions, ask harth on #qa at irc.mozilla.org.
UPDATE: mozregression has been polished up see http://harthur.github.com/mozregression
Last week I came across a bug that had snuck into Firefox sometime after 3.0. I went to go find the regression range using hg bisect but quickly realized this wouldn’t work for a regression that occurred so long ago – the dependencies for Linux had changed and building the old source was a pain. So I went to go start pinning down the range using the mozilla-central nightlies. This usually takes a couple hours and I was tired of doing this and miscalculating the bisect steps, so I wrote a python script to do practically all the work for me.
The script takes a ‘good’ date and a ‘bad’ date as arguments and will narrow down the range by executing a binary search on the mozilla nightlies, it will download each build, install it, then pop open a new window in the nightly. You do whatever you have to do to verify the bug’s presence, then enter ‘good’ or ‘bad’ into the command prompt depending on whether the bug appeared in that nightly. It will do this a few times to narrow down the range.
When you’ve checked enough nightlies (about log n nightlies, if your initial regression range is n days), you’ll see something like:
Last good nightly: 2009-06-12 First bad nightly: 2009-06-13
Which you can then paste into bugs to make people very happy (-:
Check out the installation instructions. Some future plans include:
* Automatic tests. Using them to find the regression range with no interaction required (targeting Mozmill tests first, then mochitest and the others)
* [done] Other Applications. Run other Mozilla nightlies like Thunderbird (this shouldn’t be too hard because the script uses mozrunner <3)
* Other branches. Not just mozilla-central.
* [done] Mac. Get it working on here.