1,926
edits
Firefox:1.5.0.9-2.0.0.1:Test Plan:Vista Software Update: Difference between revisions
Jump to navigation
Jump to search
Firefox:1.5.0.9-2.0.0.1:Test Plan:Vista Software Update (view source)
Revision as of 09:37, 7 December 2006
, 7 December 2006→Firefox 2.0 -> Firefox 2.0.0.1 on Vista
| Line 16: | Line 16: | ||
*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. | *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:''' | |||
== '''Jay's Results:''' == | |||
* Running Vista RC1 (Eval copy. Build 5600) | * Running Vista RC1 (Eval copy. Build 5600) | ||
* Install in Program Files dir (same results when installed in Desktop dir) | ** Install in Program Files dir (same results when installed in Desktop dir) | ||
** Check for update and get notification for 2.0.0.1 | ** 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) | ** 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). | ** 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) - STILL BROKEN: | |||
*** 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)? | |||
** 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 == | == Firefox 2.0.0.1RC1 -> Firefox 2.0.0.1nightly on Vista == | ||