Nightly Tester Tools Resurrection

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.

28 thoughts on “Nightly Tester Tools Resurrection

  1. Great news, can’t wait. Hopefully you’ll chuck in something that will copy a bug details to the clipboard so we can easily post to MozillaZine/wherever and get confirmation/etc.

  2. “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 Extension Compatibility Reporter that keeps up to date with the extension compatibility changes”.
    Please don’t take out the extension compatibility fixing! It IS the main reason many of us use NTT and the Extension Compatibility Reporter may keep up with the extension compatibility changes, but it does not fix the compatibilities issues AT ALL as NTT does. In fact it doesn’t override the incompatibilities as NTT does, so there’s a lot of add-ons I can’t really do with out that are still incompatible even having the check compatibility preference turned to false.

  3. Can you provide a working version first before adding or removing features.
    If it is not working remove it, but release soon and often…

  4. About the compatibility override:

    Unlike NTT, the Addon Compatibility reporter does not (yet) support SeaMonkey. I have been told that some future version of ACR will be compatible with some future version of Sm, but I’ll believe it when I see them. In the meantime, please don’t remove the addon compatibility override feature. Even if I know about the relevant about:config setting, not only many people don’t, but in addition it must be set again at every major alpha, beta, or final release. Also, I’m not sure whether NTT allows overriding compatibility for some addons and not others, but AFAIK about:config doesn’t (out of the box in a plain-vanilla SeaMonkey).

  5. What I did not see of either current or proposed features is the copying/inserting of a simple list of installed add-ons–sorted alphabetically, too. If you could continue to offer this utility, it would be much appreciated. Thanks.

  6. I agree, NTT is far more useful than ACR at the moment. WildcatRay, right on, as about:support copy text is not up to par as NTT, and NTT is far more competent. I also don’t understand why NTT’s options allow you to update the Window Title to whatever you like, but it doesn’t change UA Override one bit. If you can make it create Override strings instead, I could care less about displaying a custom titlebar which is kind of meaningless.

  7. I agree that the extension compatibility fixing function should not be removed. It’s far too useful for nightly testers. Some of us don’t have the ACR installed (because we are using SeaMonkey trunk) and also it’s nice to have all the features we want in one extension instead of having to install half a dozen just to get one function from extension A and one other function from extension B.

    Phil

  8. Nightly Tester Tools extension compatibility works the way I want it to.

    TBH I just plain hate Extension Compatibility Reporter, it sucks :-(

    Oh and could you have a one click for general.useragent.comptatMode.firefox = true

    Cheers!

  9. SilverWave: I don’t know which browser you’re using, but in the SeaMonkey nightlies which support it, that useragent UI is a checkbox at “Edit => Preferences => Advanced => HTTP Networking => User Agent String => [x] Advertise Firefox compatibility”. Not exactly one-click, but maybe friendlier than about:config. (Yes, a button would be welcome, but in NTT or in some other extension such as User Agent Switcher?)

    1. Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12pre) Gecko/20101013 Ubuntu/10.04 (lucid) Namoroka/3.6.12pre – Build ID: 20101013080110

      Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8pre) Gecko/20101015 Firefox/4.0b8pre Firefox-4.0/4.0b8pre

  10. I’m not sure why everyone was upset about the proposed removal of NTT’s compatibility override. I switched to ACR and it’s been more useful than NTT in that regard, because I can at least give some feedback. Instead of maintaining both NTT and ACR you should just fold them together.

    1. Not at all!!!! ACR doesn’t let you override extensions incompatibilities!!!! So I don’t find it useful because if the incompatible extension developer doesn’t care about the incompatibility of his extension, he won’t bother to update it! Instead NTT does allow you to override extensions incompatibilities so you can keep on using them!!!!

      1. Could you give an example of an extension that is incompatible with ACR? ACR turns off the compatibility check, and I haven’t found anything that I wasn’t able to install with it.

      2. I have to agree there are some misconceptions about this. The only extra benefit NTT gives is being able to override the compatibility of individual addons instead of all at once.

        ACR should let you install and use incompatible extensions.

      3. Sorry, I gave aletaziar some examples but I located my answer in the wrong place, here it is again.
        StatusbarEx is incompatible with ACR and so are Too Many Tabs, British English Dictionary, gTalk Sidebar, After the Deadline, FEBE, qtl, and Screen Capture Elite is incompatible too. I can install them, but they don’t work!!! So again, ACR doesn’t let you override extensions incompatibilities nor it turns off the compatibility check!!!

      4. Gabriela, I installed Screen Capture Elite a week ago using ACR with Firefox 4.0. It works fine. Once ACR is installed, any extension that is normally incompatible can be installed in Firefox. There will just be a note in the add-on manager telling you that it is officially incompatible – but it still works, unless the extension is broken by changes in Firefox’s code. This is better than NTT, because once you forced compatibility with that, I think it was impossible to tell from the add-on manager which extensions were compatible and which were merely forced.

  11. StatusbarEx is incompatible with ACR and so are Too Many Tabs, British English Dictionary, gTalk Sidebar, After the Deadline, FEBE, qtl, and Screen Capture Elite is incompatible too. I can install them, but they don’t work!!! So again, ACR doesn’t let you override extensions incompatibilities nor it turns off the compatibility check!!!

    1. The British English Dictionary works just fine with Firefox 4.0 and ACR. All because something is marked as Incompatible, doesn’t mean that it’s been disabled or rendered unusable. It’s merely the AOM doing it’s job and informing you that the extension isn’t designed for Firefox 4.0.

      Are you saying you’d like the ACR to remove the text that states “British English Dictionary is not compatible with Minefield 4.0a8pre”? It doesn’t make a huge difference in terms of usability, but aesthetically, it seems it could help but you at ease.

    2. Also please note, that overriding compatibility checks, does not automatically override code compatibility problems. If an extension is use dated APIs or making references to things that no longer exist or have changed. That won’t change, whether you use ACR or NTT.

      1. Seconded. Keyconfig is a good example of an extension that doesn’t work even if you override compatibility. The keyconfig window opens but there aren’t any shortcuts there. It’s just broken.

        The only extension I’ve ever encountered that simply wouldn’t install at all with NTT was SubmitToTab. That extension had been dead for years, however; I believe the add-on manager has gone through at least two drastic evolutions since it was last updated.

        To the Nightly Tester Tools Resurrection team/author, I’ll say again: it would probably be better served to just fold NTT and ACR together. NTT had one function I used regularly, and that’s overriding compatibility. As far as I remember, it was just a collection of miscellaneous features otherwise. It had an open profile shortcut, which is about the only other useful feature I remember. Your time would be wasted trying to maintain it when you already have a superior extension in ACR.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s