« Help us test the Litmus tool | Main

August 25, 2005

The road to beta - Help Us test Software Update - Firefox and Thunderbird!

We are now ready to do some testing of software update for both Firefox and Thunderbird. To that end, we have a page up on our new QA Community wiki that explains how to test the software update feature.

Please make sure to read the FAQ and to post failures to the QA blog. Please make sure to reference the known bugs and known issues listed at the bottom of the FAQ before posting failures to the blog.

So far no excitement generated by my post, so now a quick horror story for you to ponder:

Stand in front of your screen and say "Software Update" five times. What happens?

(a) Son of Candyman bursts through your computer screen and asks you for a loan to buy an iPod.

(b) Virginia Madsen contacts you and ask to be in your independent film to try to revive her career.

(c) amazon.com launches with a link to the Philip Glass CD "The music of Candyman"

Posted by marcia at August 25, 2005 02:08 PM

Trackback Pings

TrackBack URL for this entry:
http://weblogs.mozillazine.org/mt/track.cgi/4233

Comments

Did the I and II tests with update from Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050824 Firefox/1.0+ ID:2005082423:
I
B.4: There is no "Show List" Button available (probably only shown when some Extensions are incompatible?)

The C Test should better be just before the G test (easyer/less to test)

The F Test should also be right after the B Test.
F.4: There is no "Details" Button, just the clickable Text: "View more information about this update"

II
Test A and C dont work at all, it seems atm app.update.url value is simply ignored?

E: Hitting Tab key once is enough to give focus to the "Later" button.

F: Great, works ok even with Suspend to Ram!, not like known G Failure.

(L and III not tested)

I think missing in known Bugs: Wasn't it supposed to have a more descriptive Name for available Update instead of simply "Deer Park 1.0+" If I recall correctly there is already a Bug about this...

Posted by: Stebs at August 25, 2005 08:34 PM

Hiding the update pauses the update process, instead of continuing it in the background.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050824 Thunderbird/1.0+ ID:2005082408

Posted by: David at August 25, 2005 09:14 PM

Since bug 302721 landed the app.update.url setting that is set by users is now ignored so the negative tests which involve setting the update url will no longer work. Setting app.update.url.override would do what you're after now.

See https://bugzilla.mozilla.org/show_bug.cgi?id=302721#c28 for more info.

Mossop

Posted by: Mossop at August 26, 2005 05:32 AM

I'm not seeing anything in the history after applying an update. It says "No updates installed yet."

On a tangent -- what happens if a user decides not to install a particular update, preferring to skip it in favor of later one? (e.g. A nightly is known to have a major regression and I'd rather wait a day or two until it's fixed before updating.) There doesn't seem to be a mechanism to force a check after an update has been downloaded, nor a way to abandon (and not just postpone) installing a downloaded update.

Posted by: Michael Carman at August 26, 2005 06:21 AM

is app.update.url now the default to get update too work?

Posted by: RPGMaker35 at August 26, 2005 07:07 AM

Did tests running the latest nigtly build (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050825 Firefox/1.6a1)
under XP Pro SP2 (German).



I. All positive tests are OK, besides:

B: There is no "Show list" button (probably, no incompatible extensions ?)

E: If I hide download dialog and then click on "Downloading Deer Park" in menu, the download dialog reappears (this is OK). The problem is that the progress bar is not shown for a first few seconds and Kb/sec indication is completely wrong (way too high).

This is confusing (user expects to see progress bar at least at the same place where it was before the dialog was hidden).




II.

A. Failed (as mentioned by someone above, app.update.url doesn't work, and app.update.url.override has to be used instead).


B. Failed. www.mozilla.org/update shows error 403


C. Failed. Even if browser downloads index.html file (as seen by sniffer/Ethereal), error message says "AUS: Update XML File Not Found (404)" instead of "AUS: Update XML File Malformed (200)".


The remaining tests rely on app.update.url setting, which has no effect in current build.

Posted by: Alex at August 26, 2005 09:51 AM

After successful update, I clicked update history. I got message:

Deer Park 1.0+ ((nul))

Installed on:
Status:

Posted by: happ at August 26, 2005 10:41 AM

Wish to repost two possible bugs

After downloading the updates. I did't choose to restart.

Now when i go to "Help" menu it still shows "Resume Downloading DearPark 1.0+..."

I dont know if its a bug or not. But i whould expect it to display "Finished Downloading Please Restart DearPark 1.0+ Now." or just disable the menu item till user restarts the Firefox.

One More bug, when i click on "Details" link on "Software Update" Dialog its open's up a blank page.


Posted by: Yogesh Kanitkar at August 26, 2005 10:43 AM

Post a comment




Remember Me?

(you may use HTML tags for style)