Features/Desktop/Add-on hotfix/Test Plan
From MozillaWiki
< Features | Desktop | Add-on hotfix
Contents
Add-on hotfix
Release Target | Status | Lead Engineer | QA Lead | Status | Health |
Firefox 10 | Complete | Christian Legnitto | VladG | Landed | OK |
Summary
Firefox will have a hardcoded add-on id. When checking for add-on updates (every 24 hours), it will always check for a specific add-on id and install it if an update is found.
Use Cases to Test
- We ship a new feature (like http:// hiding) and the user response is extremely negative. We issue an update to the add-on that flips a pref back to old behavior
- We need to distrust a CA. We ship an update to the add-on that makes Firefox distrust it and users are silently updated within 24 hours
- We have a problem with add-ons that require a rebuild of add-on metadata. We issue an empty add-on
- We have an issue that only affects Italian builds. Rather than issue a new Firefox update to everyone, we ship an update to the add-on which only acts when the locale is set to Italian
- We want to blocklist a widely used plugin. We turn on crude click-to-play and whitelist it for known good websites
- We know that Netflix/Hulu/etc does bad user sniffing for a particular Firefox version. We issue an update that drops down a infobar telling users what is happening and to contact the site, or we ship the add-on that changes the user agent on the site while they work on a fix
- We want to speak directly to our users with a one-time marketing message / news flash. We ship an update to the add-on that pops up an infobar with the message and then never shows again
- We want to A/B test a UI pref on beta. We ship the add-on to x% of our population or ship it to all Beta users and have the add-on enable functionality x% of the time
New Bugs
Bug ID | Summary | Reporter | Status |
bug 727398 | Mozilla Firefox Hotfix is listed in Add-ons Manager even though it shouldn't | VladG | NEW |
Test Case 1 - installing the add-on
Steps to reproduce
- Start Firefox with a new profile
- In about:config set the following prefs:
- set extensions.hotfix.id to test-hotfix@mozilla.org
- set extensions.update.interval to 10
- Restart Firefox
Expected Results
- After restart, navigate randomly over 10 seconds
- Open Add-ons Manager and Firefox Hotfix Test 1 should be installed
Firefox 10 Beta 4
- [DONE] MacOS X 10.6.7 - PASS - 2012-01-13
- [DONE] Windows 7 x86 - PASS - 2012-01-13
- [DONE] Ubuntu 11.10 x64 - PASS - 2012-01-13
- [DONE] Windows XP - PASS - 2012-01-13
Test Case 2
- This test checks that none of the four test add-ons are installed.
- You will have to run the steps from below for four times, changing the extension's ID accordingly:
- Hotfix Test Broken's ID: test-hotfix-broken@mozilla.org
- Hotfix Test Incompatible's ID: test-hotfix-incompatible@mozilla.org
- Hotfix Test Self Signed's ID: test-hotfix-selfsigned@mozilla.org
- Hotfix Test Unsigned's ID: test-hotfix-unsigned@mozilla.org
- Do not install manually.
Steps to reproduce
- Start Firefox with a new profile
- In about:config set the following prefs:
- set extensions.hotfix.id to test-hotfix-"extension's ID"@mozilla.org
- set extensions.update.interval to 10
- Restart Firefox
Expected Results
- After restart, navigate randomly over 10 seconds
- None of the add-on should be installed
Firefox 10 Beta 4
- [DONE] MacOS X 10.6.7 - PASS - 2012-01-16
- [DONE] Windows 7 x86 - PASS - 2012-01-16
- [DONE] Ubuntu 11.10 x64 - PASS - 2012-01-16
- [DONE] Windows XP - PASS - 2012-01-16
Test Case 3 - removing and reinstalling the add-on
Steps to reproduce 1
- Start Firefox with a new profile
- In about:config set the following prefs:
- set extensions.hotfix.id to test-hotfix@mozilla.org
- set extensions.update.interval to 10
- Restart Firefox
- After Firefox Hotfix Test 1 is installed, remove it from the Add-ons Manager. Do not restart the browser yet.
Expected Results
- The Add-on should get removed with the "undo" function active.
- Pressing the "undo" should keep the add-on installed.
- After Firefox restarts, the add-on should be deleted.
Steps to reproduce 2
- Start Firefox with a new profile
- In about:config set the following prefs:
- set extensions.hotfix.id to test-hotfix@mozilla.org
- set extensions.update.interval to 10
- Restart Firefox
- After Firefox Hotfix Test 1 is installed, remove it from the Add-ons Manager and restart Firefox.
- In about:config, reset the pref extensions.hotfix.lastVersion
- Restart Firefox
Expected Results
- After restart, navigate randomly over 10 seconds
- Open Add-ons Manager and Firefox Hotfix Test 1 should be installed
Steps to reproduce 3
- Start Firefox 10b5 with a new profile.
- Manually add to Firefox the Hotfix Test Add-on 1
- Set the folowing prefs in about:config:
- set extensions.update.interval to 10
- in extensions.update.url replace versioncheck.addons.mozilla.org from the string with addons-dev.allizom.org
- Restart Firefox and wait for about 90 sec
Expected Results
- After ~90 sec the test add-on should be removed.
Firefox 10b5:
- [DONE] MacOS X 10.6.7 - PASS - 2012-01-20
- [DONE] Windows 7 x86 - PASS - 2012-01-20
- [DONE] Ubuntu 11.10 x64 - PASS - 2012-01-20
- [DONE] Windows XP - PASS - 2012-01-20
Test Case 4 - removing Hotfix1 test add-on
Steps to reproduce
- Install the Hotfix v1 in Firefox 10 beta
- Change the update channel to "releasetest" and perform an update to Firefox 11 beta
- In about:config set the following prefs:
- set extensions.update.interval to 10
- in extensions.update.url replace versioncheck.addons.mozilla.org from the string with addons-dev.allizom.org
- Restart and browse for several minutes
Expected results
After browsing for several minutes, the Hotfix v1 add-on that was previously installed should be automatically deleted.
Firefox 11b2:
- [DONE] MacOS X 10.6.7 - PASS - 2012-02-13
- [DONE] Windows 7 x86 - PASS - 2012-02-13
- [DONE] Ubuntu 11.10 x32 - PASS - 2012-02-13
- [DONE] Windows XP - PASS - 2012-02-13