New add-on management and testing strategy

[flod]

I saw that a couple of important bugs just landed on central

*Bug 596343* <https://bugzilla.mozilla.org/show_bug.cgi?id=596343>
-Users should have exclusive control over selecting their add-ons
*Bug 476430* <https://bugzilla.mozilla.org/show_bug.cgi?id=476430> -Make
third-party add-ons disabled on startup, and allow users to activate them

Is there any "testing strategy" for this? I mean, it's kind of difficult
to test all those strings. IMO at least we need:

* to know how to force that window to display
* an extension compatible with nightlies
* an extension not compatible but with a compatible update available
* an extension not compatible without available updates
* some sort of third party software that tries to install an extension
in Firefox

Francesco

[smo]

On Aug 13, 8:34 am, flod <li...@lodolo.it> wrote:
...

>   * to know how to force that window to display

...
> Francesco

Rang a bell with me right away: localizers in SuMo have exactly the
same problem: how do I get a display of a native msgbox saying
".....bla bla bla is forced to close due to bla bla bla ...." if my
current Firefox is sailing without any problems?

regards

smo

[flod]

Il 14/08/11 09.32, smo ha scritto:

> Rang a bell with me right away: localizers in SuMo have exactly the
> same problem: how do I get a display of a native msgbox saying
> ".....bla bla bla is forced to close due to bla bla bla ...." if my
> current Firefox is sailing without any problems?

To crash Firefox there's an extension
http://code.google.com/p/crashme/

For testing plugin crashes when OOOP was introduced we used a site
(http://flashcrash.dempsky.org/) but it's not working anymore. AFAIK
there's not an equivalent of crashme.xpi for that.

Francesco

[Axel Hecht]

Dave, I know you talked about testing l10n builds as a follow up, do you
have any hints for this?

Thanks

Axel

[Reuben Morais]

> Rang a bell with me right away: localizers in SuMo have exactly the
> same problem: how do I get a display of a native msgbox saying
> ".....bla bla bla is forced to close due to bla bla bla ...." if my
> current Firefox is sailing without any problems?

When I'm translating that kind of stuff on SuMo I normally look at the
l10n files (MXR to find where the original string is located, then
look in the appropriate locale for the translation).
Maybe we should have an article explaining how to use MXR, how the hg
repo is structured, etc so localizers who are not familiar with them
can use the same technique?

--
Reuben

[flod]

Il 14/08/11 12.25, Axel Hecht ha scritto:

> Dave, I know you talked about testing l10n builds as a follow up, do
> you have any hints for this?

Hi Axel,
Dave = Dave Townsend? Did you planned to add him in cc?

Anyhow, I discovered that changing these two keys in about:config makes
the "Selection window" reappear
> extensions.shownSelectionUI -> false
> extensions.lastAppVersion -> 8.0a1
At least is a start.

Francesco

[Dave Townsend]

Yeah we talked about me making some kind of mozmill test available that did basically the below. I intend to do that but it's likely I won't be able to start till later this week. For now just setting extensions.lastAppVersion to something old and making sure extensions.shownSelectionUI is false if it is there at all will make the UI appear on next startup. I can't name extensions that fill out all the cases he mentions below off the top of my head, the mozmill test would use tricks to make all those cases exist.

Bug 476430 is pretty easy to test manually though, disable an extension then restart Firefox, then navigate to about:newaddon?id=<ID> for the extension and you'll see the UI.

[flod]

Hi Dave,
I found a small problem in the UI, not sure if I should comment in the
original bug or open a new one.

In the second page of the wizard, in the lower part of the window
there's the string "You can always change your add-ons by going to the
Add-ons Manager." and two buttons ("Back" and "Done").

Is it possible to make that string wrap? Right now, having a very long
translation, I have to use a huge width for the entire window (130ch
instead of 100ch) just to ensure that those two buttons are not cut.

Francesco

[Dave Townsend]

Please file a new bug for that (almost always problems identified should be filed as new bugs)

[Dave Townsend]

On 8/17/11 22:33, Dave Townsend wrote:
> Yeah we talked about me making some kind of mozmill test available that did basically the below. I intend to do that but it's likely I won't be able to start till later this week. For now just setting extensions.lastAppVersion to something old and making sure extensions.shownSelectionUI is false if it is there at all will make the UI appear on next startup. I can't name extensions that fill out all the cases he mentions below off the top of my head, the mozmill test would use tricks to make all those cases exist.

Took me longer than I had planned but I've just posted a mozmill script
at https://bugzilla.mozilla.org/show_bug.cgi?id=596343#c182 which will
allow you to open the UI with a number of add-ons in various states to
play with. It's possible to make it more automated with screenshot
taking and such but it feels to me like just being able to play with the
UI in this way is probably best. Let me know if I'm wrong or if there
are other things that would be useful here.