QA/mozilla-aurora/fx5/Beta Merge/Updates Testing

From MozillaWiki
< QA‎ | mozilla-aurora‎ | fx5‎ | Beta Merge
Jump to: navigation, search

« mozilla-aurora | mozilla-aurora:fx5 | mozilla-aurora:fx6 »

Firefox 5.0b2 Software Updates

How to Test Partial, Complete, and Fallback Updates

To test partial, complete, and fallback updates:

  • Complete: All updates will be done as completes. This refers to testing an update from the immediate last release, in this case going from 5.0b1 to 5.0b2, and from 4.0bX and 4.0.1b to 5.0b2
  • Fallback: For this you first get whatever update the usual way, but you don't apply it. Then you test that it can get fetch another copy of the update if something were to go wrong. You do this by:
  1. Checking for updates. Choose to apply later. Close application.
  2. Then go the C:\Documents and Setting\<user profile>\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox\updates\0\ folder, in WinXP for instance. Inside you will find a file called 'update.status'.
  3. If you are in Vista the update.status file will be in ...AppData/Local/Mozilla Firefox/updates/0/
  4. Open it with a text editor and replace the string from pending to 'failed'. Restart the app and make sure you get another copy of the update.

Software Updates

Windows 7 (tester) Windows XP (tester) Mac OS X (tester) Linux (tester)
5.0b1 en-US (complete+fallback)
en-US (complete+fallback)
en-US (complete+fallback)
en-US (complete+fallback)
4.0.1 en-US (complete+fallback)
es-ES (complete+fallback)
en-US (complete+fallback)
fr (complete+fallback)
en-US (complete+fallback)
ja-JP-mac (complete+fallback)
en-US (complete+fallback)
de (complete+fallback)
4.0rc1 en-US (complete+fallback)
es-ES (complete+fallback)
en-US (complete+fallback)
fr (complete+fallback)
en-US (complete+fallback)
ja-JP-mac (complete+fallback)
en-US (complete+fallback)
de (complete+fallback)
4.0b12 en-US (complete+fallback)
de (complete+fallback)
en-US (complete+fallback)
es-ES (complete+fallback)
en-US (complete+fallback)
ja-JP-mac (complete+fallback)
en-US (complete+fallback)
zh-TW (complete+fallback)
4.0b8 en-US (complete+fallback)
de (complete+fallback)
en-US (complete+fallback)
es-ES (complete+fallback)
en-US (complete+fallback)
ja-JP-mac (complete+fallback)
en-US (complete+fallback)
zh-TW (complete+fallback)
  • Locales known to not receive update (intentional):
    • ak, bg, bn-BD, cy, es-AR, id, ja, ja-JP-mac, ku, mk, nn-NO, or, sr, ta, ta-LK, th, vi

Detailed Results

  • path, locale, type (partial, complete, fallback), date: result
    • Build ID: Mozilla/5.0 (Macintosh; U; Intel Mac OS X... for example

Betatest

Mozmill Results: PASS

5.0b1 4.0.1 4.0rc1 4.0b12 4.0b8 Build ID
Win2k PASS PASS PASS PASS PASS 20110517192056
WinXP PASS PASS PASS PASS PASS 20110517192056
Vista PASS PASS PASS PASS PASS 20110517192056
Win7 PASS PASS PASS PASS PASS 20110517192056
Win7 64-bit PASS PASS PASS PASS PASS 20110517192056
Mac OSX 10.6 PASS PASS PASS PASS PASS 20110517192056
Ubuntu 10.10 32-bit PASS PASS PASS PASS PASS 20110517192056
Ubuntu 10.10 64-bit PASS PASS PASS PASS PASS 20110517192056

Releasetest

We inadvertently skipped this check in the morning. What we check during updates testing in the releasetest channel is to make sure that updates are offered through mirrors, no broken ones, and that there's enough saturation. Enough time passed since 7am that we should have had a problem with mirror saturation.

Beta

Mozmill Results: PASS

5.0b1 4.0.1 4.0rc1 4.0b12 4.0b8 Build ID
Win2k PASS PASS PASS PASS PASS 20110517192056
WinXP PASS PASS PASS PASS PASS 20110517192056
Vista PASS PASS PASS PASS PASS 20110517192056
Win7 PASS PASS PASS PASS PASS 20110517192056
Win7 64-bit PASS PASS PASS PASS PASS 20110517192056
Mac OSX 10.6 PASS PASS PASS PASS PASS 20110517192056
Ubuntu 10.10 32-bit PASS PASS PASS PASS PASS 20110517192056
Ubuntu 10.10 64-bit PASS PASS PASS PASS PASS 20110517192056