The MozQA community is holding a Testday on Friday, June 11th, for users interested in the use, development and/or testing of the new Addons Manager for Firefox 4. We’re going to have the awesome Firefox QA and development team available to help users perform exploratory testing for that new feature and just generally chat about it with the community via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you’re interested, come on by anytime between 1AM to 5PM PDT that Friday!
How to Get Started
To start running tests of any sort against the new Add-ons Manager simply requires a latest nightly build for the upcoming Firefox 4. Just grab a build from the FTP site, install it in parallel to your default Firefox installation, and also use a separate profile for testing. That’s it!
Note: To test different available extensions from addons.mozilla.org or other websites you should disable the “extensions.checkCompatibility.3.7a” preference in about:config. You can also install the developer version of the Add-ons Compatibility Reporter which sets all the needed hidden preferences automatically.
Details
Since our last Add-ons Manager testday, on April 24th, a lot of bug fixes and improvements have been checked into our development branch. We have to say thanks again to everyone who has participated in that event and gave us those fantastic results. We hope the next testday will be attended in a similar manner.
As what we have done last time, we will do again but with a much larger set of exploratory tests. Therefore you should have a look at our feature tracking spreadsheet which lists any area of testing for the new Add-ons Manager. Select one of those areas and think about which particular tests should be run against it. Execute all of those tests and once you have found an issue, it should be discussed on IRC and filed as a new bug on Bugzilla.
Areas which need the most attention during the testday are:
Installing, enabling, disabling, and removing any kind of extension
Areas we don’t have to work with:
The “Get Add-ons” pane is still under development. The currently available version is a placeholder only.
The details panes for all types of add-ons are still placeholders for the real data pulled from AMO.
How will the testing work during the testday:
To make sure that we cover each specific area we wanna track our work in the testday spreadsheet. Make sure to assign yourself to a given area and start with exploratory testing. Any bugs you have found should be filed on Bugzilla. Make sure that there isn’t already a bug for it by checking all known bugs.
The MozQA community is holding a Testday on Friday, June 11th, for users interested in the use, development and/or testing of the new Addons Manager for Firefox 4. We’re going to have the awesome Firefox QA and development team available to help users perform exploratory testing for that new feature and just generally chat about it with the community via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you’re interested, come on by anytime between 1AM to 5PM PDT that Friday!
How to Get Started
To start running tests of any sort against the new Add-ons Manager simply requires a latest nightly build for the upcoming Firefox 4. Just grab a build from the FTP site, install it in parallel to your default Firefox installation, and also use a separate profile for testing. That’s it!
Note: To test different available extensions from addons.mozilla.org or other websites you should disable the “extensions.checkCompatibility.3.7a” preference in about:config. You can also install the developer version of the Add-ons Compatibility Reporter which sets all the needed hidden preferences automatically.
Details
Since our last Add-ons Manager testday, on April 24th, a lot of bug fixes and improvements have been checked into our development branch. We have to say thanks again to everyone who has participated in that event and gave us those fantastic results. We hope the next testday will be attended in a similar manner.
As what we have done last time, we will do again but with a much larger set of exploratory tests. Therefore you should have a look at our feature tracking spreadsheet which lists any area of testing for the new Add-ons Manager. Select one of those areas and think about which particular tests should be run against it. Execute all of those tests and once you have found an issue, it should be discussed on IRC and filed as a new bug on Bugzilla.
Areas which need the most attention during the testday are:
Areas we don’t have to work with:
How will the testing work during the testday:
To make sure that we cover each specific area we wanna track our work in the testday spreadsheet. Make sure to assign yourself to a given area and start with exploratory testing. Any bugs you have found should be filed on Bugzilla. Make sure that there isn’t already a bug for it by checking all known bugs.
Details
Venue