Firefox:1.5.0.9-2.0.0.1:Test Plan:Vista Software Update: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 26: Line 26:


* en_windows_vista_x86_dvd_X12-34293.iso from http://fs
* en_windows_vista_x86_dvd_X12-34293.iso from http://fs
** 2.0 -> 2.0.0.1 (unsigned, releasetest channel) - STILL BROKEN:
** 2.0 -> 2.0.0.1 (unsigned, releasetest channel) - PASS
*** The new updates TR created tonight still do not work.  I see the same behavior as I did before.  Firefox appears to download the partial patch quickly, but fails to apply on restart...and then retries a complete udpate which also fails.  So not sure if the SHA1 hash fix worked...  TR, please look into this and figure out what is broken... hopefully we don't have to go through this cycle again (don't you guys have automation that quickly checks to make sure these kinds of issues don't get to QA)?
*** Only worked for me when using "Run as administrator".


** 2.0 -> 2.0.0.1 (signed, betatest channel) - PASS:
** 2.0 -> 2.0.0.1 (signed, betatest channel) - PASS:

Revision as of 21:37, 7 December 2006

For this release we will be signing the files that are installed in Firefox 2.0.0.1 (not all of them), and this will be the first time we do an update in Vista in the 2.0 branch. We will track our testing results here. These tests are time sensitive; these updates are in place as of 12/05, but they might change as the "real" updates are generated.

Firefox 2.0 -> Firefox 2.0.0.1 on Vista

Take a released version of FF2 and edit the release channel to "betatest". Then check for updates and make sure it finds one and that it is downloaded and applied. In addition, the files in the installation folder should be signed (Right Click->Properties->Digital Signatures). Neither any of the *.chk nor the nss* files should be signed (ask preed as to why).

Results:

  • FF2.0->FF2.0.0.1: Failed
  • Update is found and apparently downloaded, but it is not applied. The mar file is not in the usual location after the apparent download, but the update history in the Advanced Preferences shows that the installation is pending.
  • Also noticed that if you install on a folder in the desktop the mar file will be downloaded, but it won't be applied. It will keep trying to download and apply after you click on "restart."

Marcia's Results:

  • FF2.0->FF2.0.0.1: Failed

Running Win Vista Build 5728 on the Win vista laptop I have.

  • Update is found and downloads (complete) and I am asked to restart Firefox. When I restart, Firefox does not restart and the update has not been applied. The updates file folder is empty.


Jay's Results:

  • Running Vista RC1 (Eval copy. Build 5600)
    • Install in Program Files dir (same results when installed in Desktop dir)
    • Check for update and get notification for 2.0.0.1
    • Start download and watch progress of 7.2MB file (.mar and .status files are generated in /updates/0 dir)
    • After restart, patch fails to apply and "full" update process begins (which also fails on restart).
  • en_windows_vista_x86_dvd_X12-34293.iso from http://fs
    • 2.0 -> 2.0.0.1 (unsigned, releasetest channel) - PASS
      • Only worked for me when using "Run as administrator".
    • 2.0 -> 2.0.0.1 (signed, betatest channel) - PASS:
      • I was able to successfully update 2.0->2.0.0.1 on the betatest channel (to signed 2.0.0.1 rc1 build)... but need to know how I can verify that I ended up with "signed" files.
      • The only interesting thing to note about the update is that after restart, I was asked by Vista if I wanted "updater.exe" to do it's thing...and I had to grant permission. I'm assuming this is expected behavior?


NOTE: In both update cases above, I noticed (once again) that I cannot edit the channel-prefs.js file to modify the update channel in the default location in the Firefox install directory (I have to copy to my Desktop, edit, and then move it back). I'm assuming this is some sort of new "security" feature in Vista...which is kind of annoying in this case, but is probably a good thing overall. Can someone else confirm that this is expected behavior?

Firefox 2.0.0.1RC1 -> Firefox 2.0.0.1nightly on Vista

Take the release candidate and edit teh release channel to "betatest". Then check for update and makes sure it finds, downloads, and applies it. At this time the files should not be signed.

Results:

  • FF2.0.0.1RC->FF2.0.0.1nightly: Failed
  • Similar as above.