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

Jump to navigation Jump to search
No edit summary
Line 24: Line 24:


== '''Jay's Results:''' ==
== '''Jay's Results:''' ==
* 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"... but probably because I installed in in a non-standard app directory (/FF20_unsigned_update instead of /Mozilla Firefox).
** 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).
*** I also updated 2.0.0.1->2.0.0.1 nightly on the same channel.
*** I installed in the standard "Mozilla Firefox" app directory and was prompted  with UAC dialogs to allow updater.exe to complete the update.


* Running Vista RC1 (Eval copy. Build 5600)
* Running Vista RC1 (Eval copy. Build 5600)
Line 30: Line 39:
** 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).
** '''NOTE''':  This testing was done without any knowledge about the expected behavior with Vista and is only here for reference... I don't recall exactly where I installed Firefox, but know that I did not do anything special during my testing ("Run as admistrator", etc).


* en_windows_vista_x86_dvd_X12-34293.iso from http://fs
'''NOTE:''' In both update cases above, I noticed 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).  This appears to be standard behavior with UAC enabled on Vista.
** 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?


== Tomcat`s result ==
== Tomcat`s result ==
1,926

edits

Navigation menu