You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

You are here: browser/composer front-end test cases > Test documentation for helper application UI

Test Documentation for Helper Application UI

Maintained by Chris Petersen

Helper applications are programs launched from Mozilla (or Netscape) which allow you to view or handle non-webpage files. Some examples include RealPlayer audio or movie files or compressed binary (.zip, .bin, .gz) files. This QA document covers how the browser (Navigator) should function with system-defined and user-defined helper applications, as well as when encountering undefined/unknown file types.

What will be tested

Test coverage will focus primarily on front-end (UI) features, and will include:

  • How helper applications are handled/encountered from the browser UI.
  • Navigator launching/use of OS-defined helper applications
  • Navigator launching/use of user-defined helper applications
  • The Helper Application (aka, "Downloading") dialog
  • Preferences for helper applications
  • How Navigator deals with unknown/undefined file types
  • Test on the main platforms: Win32, Mac OS and Linux
  • Overall look and feel:
  • Appearance, highlighting, navigation, modality: menu items and dialogs.
  • Spelling, typos, grammar of any text/descriptions

What will NOT be tested

There are some other areas which are related to helper applications, but they are either covered by other QA groups, or cannot be covered due to time constraints. In addition, there are some areas which might seem related (from an end-user perspective), but really aren't. I've listed the possible areas below -- along with relevant Bugzilla components which might help narrow down who works on what. (Unless otherwise noted, these components reside under the Browser product.)

  • Saving/downloading of files from the browser is covered by the downloading UI test page. However, like helper applications, many bugs are typically filed under File Handling. Some might be filed under the Networking components as well.
  • Back-end aspects of helper application and MIME type handling.
  • Helper applications can be opened from mail. Bugs belong in either the Mail Back End, MIME or Mail Window Front End components of the MailNews product.
  • Plug-ins (eg, QuickTime, Macromedia' Flash) are a separate area and issues there belong in the Plug-ins component.

Issues, references & bug information

Most helper application bugs can be found within the File Handling browser component of Bugzilla. You will probably need to search either (or both) the summary or comments (details) for strings such as "helper apps" or "mimetypes".

Here are some known bugs which interfere with the usage and/or testing of helper applications:

  • 54940: Unlike in Communicator (Netscape 4.x), OS-defined helper applications are not displayed within the Helper Applications preference panel. For example, bug 68515 (and 68514) are Mac OS-oriented bugs which call for utilizing Internet Config settings to provide such information.
  • The matrix below currently based on the design in bug 88066. So, when the helper app download --or other related UI-- changes, this matrix should be updated.
  • Platform differences. Mac OS behavior (expected):
    • After quitting Mozilla/Netscape, files that had been downloaded into the default download folder are not deleted -- unlike on Win32 or Unix.
    • The option in the download progress dialog, "Keep window open after download is complete", is not available when opening files with helper apps. The download progress dialog closes automatically when done with downloading the file locally. Again, unlike on Win32 or Unix.
  • 93173: Helper app decision properly isn't remembered when using Open for non-OS-defined types.
  • 112180: Long path displayed in helper app ("downloading") dialog results in poor dialog display, as well as Helper Applications pref panel inaccessibility.
  • 111035: Need to remember the user selection for the "Open using" radiobutton.
  • 132456: The download manager window opens when opening a file with a helper application.
  • If/when you click on an .exe file on Win32, you won't get the helper app dialog. Instead you'll immediately get saving [file picker] dialog to select a location to download. This is by design for security reasons, since clicking a link should not cause another application to run without warning the user. AFAIK, this is the case for both trunk and branch commercial builds -- maybe also for mozilla trunk/branch, but should doublecheck if you're curious. See bugs 116938 and 158623 for more details.
  • The download progress dialog will sometimes appear clipped -- esp on Macintosh. See bug 79889.

Test coverage & outline

Notes on testing:

  • The sample filetypes I've used are dependent on the setup of my machines, notably the OS-defined settings on Win32 and Mac OS. YMMV.
  • Having said that, here are some sample test locations (some links are internal):
    • http://mozilla.org/ -- check out the links under Nightly Builds; the next one might be better...
  • I typically remove the filetypes from the Helper Applications preferences panel before creating another one of this same type (since I tend to reuse them). Doing this in the past made bug 88287 appear (now fixed) -- just follow the workaround there: exit the app, restart, immediately remove the type, then immediately exit app.
  • In the download progress dialog, the Pause/Resume buttons are only available for ftp downloads. You won't see 'em for http downloads, even if you go through the helper app dialog.

Acceptance tests

Very simple sanity tests. Best to do these with a fresh (new) profile.

  • Access to Helper Applications ("Downloading") dialog.
  • Helper Applications preferences.

Functional tests

The matrix below provides baseline functionality coverage.

In addition, you can generate your own test files using the Handy Content Generator (internal server access only):

  1. Do this if testing user-defined helper apps; skip if you want to test OS-defined ones, if applicable. Create a helper app entry in the Helper Application preferences panel. For example:
    • Enter an extension (eg, ram).
    • Enter a mimetype (eg, audio/x-pn/realaudio).
    • Enter the path to an application to launch (eg, the path the Real Player).
  2. Go to http://law.mcom.com/gimme.html (clicking here will open another window).
  3. In that web page, you can directly serve up the content via either a CGI script (click the "via gimme.cgi" button), or an .exe (click the "via gimme.exe" button). An explanation of the form's fields:
    • Enter a mimetype in the "What content-type do you want?" field (eg, application/octet-stream).
    • Enter the size of the file you want served up in the "How many bytes of content do you want?" field (eg, 256, 1024, etc).
    • Optional, but useful. Enter your own filename in the "reply headers you want sent" textarea (eg, Content-Disposition: attachment; filename="sample.bin" would override the default filename, and set it to sample.bin).
Task/Existing conditions Linux [unix] Win32 Macintosh
Nouser-defined mimetype &&
No OS-defined mimetype
 Test cases:
  • using Save radiobutton
  • using Open radiobutton
example: try an .mp3 file; test open with /usr/bin/xmms.
 Test cases:
  • using Save radiobutton
  • using Open radiobutton
example: try a .bin or .bz2 file.
 Test cases:
  • using Save radiobutton
  • using Open radiobutton
examples: try an .exe, .doc or .bz2 file...

bug 97707 : setting for Open button shouldn't persist.
No OS-defined mimetype &&
With user-defined mimetype from
Helper Applications preferences panel
 example:
use .mp3 file, audio/mpeg, open with /usr/bin/xmms.
 example:
use a .bin or .bz2 file, application/octet-stream, open with WinZip.
 examples:
use an .exe file, application/octet-stream, open with StuffIt Expander.

bug 98296 : this test fails on 9/X.
No OS-defined mimetype &&
With user-defined mimetype from
Advanced button in helper app dialog
 example:
use .mp3 file, audio/mpeg, open with /usr/bin/xmms.
 example:
use .bin or .bz2 file, application/octet-stream, open with WinZip.
 examples:
use a .pdf file, application/pdf. open with Adobe Acrobat Reader; or, an .exe file, application/octet-stream, open with StuffIt Expander.
No user-defined mimetype &&
With OS-defined mimetype
 example:
if you RealPlayer installed, try testing with .wav, and/or .ram or .rm files.
 examples:
use .rm or .ram file to test RealPlayer. also, use .mp3 to test Winamp.
 example:
use .rm or .ram file to test RealPlayer.
Helper application dialog:
"Always ask before opening this type of file" checkbox and "Reset" button in pref panel.
 Test with this setting on [default].

Test with this setting off.

Also test the Reset button in the Helper Apps pref panel, which would turn this setting back on.

Will also likely see regression bug 93173 .
 Test with this setting on [default].

Test with this setting off.

Also test the Reset button in the Helper Apps pref panel, which would turn this setting back on.

Will likely see regression bug 93173 .
 Test with this setting on [default].

Test with this setting off.

Also test the Reset button in the Helper Apps pref panel, which would turn this setting back on.

Will likely see regression bug 93173 .

Stress, boundary, negative, etc.

Under construction

Ad hoc & regression testing

Ad hoc testing is covered by users in the Internet community, as well as casual use. Due to time constraints, regression testing will encompass:

  • Verification of Resolved (Fixed ones get priority) bugs as they come in.
  • Periodic verification (eg, milestone deadlines) of Big Issues to make sure they're still fixed. This would go hand in hand with the usual testing that occurs during those periods.
  • Ad hoc testing with daily builds.