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.



You are here: Browser/Composer front-end QA > front-end test cases > Test documentation for cmd-line

Test Documentation for Command-line Features

by Sarah Liberman <sairuh@aol.net>

This plan covers features which are accessed at the command line in a Linux/unix or Win32 console, or as a Mac OS shortcut.

Will test

The test areas here are pretty straightforward. Basically test for:

  • Results of commands issued in a Linux/unix or Win32 console.
  • Results of launching the shortcuts on the Macintosh platform.

Will not test

The following areas will not be covered. Testing is so far limited to making sure that commands actually launch as expected. However, testing the resulting features isn't necessarily covered here. Please refer to the appropriate test document for further information. In addition, I've denoted which Bugzilla component these items are likely to fall under; unless otherwise noted, the components are in the Browser product.

  • X-remote - Bugs go to the X-remote component
  • GTK or X11 options
  • Profile management, including
    • Migration - Bugs go to Profile Migration
    • Creation - Bugs go to Profile Manage BackEnd
    • Selection - Bugs go to Profile Manage FrontEnd
  • Newsgroups - Bugs go to the Mail Window Front End component of the MailNews product
  • Mail - bugs go to the MailNews product, including
    • Mail & News window - Mail Window Front End component
    • Message composition - Composition component
    • Address book - Address Book component
  • Composer - Bugs go to the Editor: Composer component
  • JavaScript - Bugs go to either JavaScript Console or JavaScript Debugger
  • IRC - Mozilla only; bugs go to the Chatzilla component
  • AIM - Netscape only, so bugs belong in the Instant Messenger product of Bugscape

Issues, references & bug information

These features have been lightly tested by QA, so your input is greatly welcomed!

The following are two useful references:

Also check out open bugs currently under XP Apps: Cmd-line Features, sorted by severity.

Test coverage

Test coverage includes:

Couldn't find a particular test scenario here? I encourage you to send additions, corrections and suggestions!

Acceptance tests

Acceptance testing of command-line features basically comprise unit tests of the more common options. This would, for example, include -P, -mail, -ProfileManager, -edit, as well as simply appending <url> after the ./mozilla command.

On the other hand, functional testing (refer to the platform-specific sections below) comprises a couple things:

  • Testing less commonly used options.
  • Testing combinations of options given issued at once, such as
./mozilla -P <profile> -mail
Launches the Mail & News window of the specified profile.

If you're testing in a multi-profile situation, most command-line options will result in initially displaying the Profile Manager -- unless you have already specified a given profile (-P <profile>) to use as well. After selecting a given profile, then the command should launch as expected.

Mac OS command files

For Mac OS, the following shortcuts are covered. Netscape is the same, except that the shortcuts are named "Netscape Profile Migration" and so forth. These are tested by dragging the appropriate icon onto the Mozilla application icon.

  • Mozilla Profile Manager. Starts with the Profile Manager.
  • Mozilla Profile Migration. Starts with the 4.x migration window.

Win32 command-line options

Here are options for the Win32 platform, with their expected behaviors. Unless otherwise noted, all of this commands are case-insensitive.

  • <url> Appending a URL will launch the browser and load that URL.
  • -h, -help. Displays commands with brief descriptions.
  • -console. Displays console while running.
  • -installer. Launches the 4.x migration window.
  • -height <value>, -width <value>. Sets height and width of startup window to <value>'s.
  • -v, -version. Displays version information in the console.
  • -CreateProfile <profile>. Creates <profile>, but does not launch it.
  • -ProfileWizard. Launches the Profile Wizard.
  • -ProfileManager. Launches the Profile Manager.
  • -P <profile>. Starts with <profile>.
  • -SelectProfile. Launches the Select User dialog.
  • -nosplash , -quiet. Suppresses display of the splashscreen.
  • -news. Launches the Mail & News window, displaying the default news account.
  • -mail. Launches the Mail & News window, displaying the default mail account.
  • -addressbook. Launches the Address Book window.
  • -compose to=foo@nowhere.net,subject=Cool%20page,attachment=www.mozilla.org,body= check%20this%20page... Launches the Mail compose window, including those options for the message, if supplied.
  • -editor, -edit <url>. Starts the editor for the given <url> (where <url> is optional).
  • -chrome <url>. Launches and loads the given chrome <url>.
  • -UILocale <locale>. Start with <locale> resources as UI Locale.
  • -contentLocale <locale>. Start with <locale> resources as content Locale.
  • -chat. Starts with the IRC client, Chatzilla, if installed.
  • -jsconsole. Starts with the JavaScript console.

Unix (Linux) command-line options

Here are options for the Win32 platform, with their expected behaviors. Unless otherwise noted, all of this commands are case-insensitive.

  • <url> Appending a URL will launch the browser and load that URL.
  • -h, -help. Displays commands with brief descriptions.
  • -console. Displays console while running.
  • -installer. Launches the 4.x migration window.
  • -height <value>, -width <value>. Sets height and width of startup window to <value>'s.
  • -v, -version. Displays version information in the xterm.
  • -CreateProfile <profile>. Creates <profile>, but does not launch it.
  • -ProfileWizard. Launches the Profile Wizard.
  • -ProfileManager. Launches the Profile Manager.
  • -P <profile>. Starts with <profile>.
  • -SelectProfile. Launches the Select User dialog.
  • -splash. Starts with displaying the splashscreen.
  • -news. Launches the Mail & News window, displaying the default news account.
  • -mail. Launches the Mail & News window, displaying the default mail account.
  • -addressbook. Launches the Address Book window.
  • -compose to=foo@nowhere.net,subject=Cool%20page,attachment=www.mozilla.org,body= check%20this%20page... Launches the Mail compose window, including those options for the message, if supplied.
  • -editor, -edit <url>. Starts the editor for the given <url> (where <url> is optional).
  • -chrome <url>. Launches and loads the given chrome <url>.
  • -UILocale <locale>. Start with <locale> resources as UI Locale.
  • -contentLocale <locale>. Start with <locale> resources as content Locale.
  • -chat. Starts with the IRC client, Chatzilla, if installed.
  • -jsconsole. Starts with the JavaScript console.
  • -remote <command>. Execute remote command in an already running Mozilla process.

GTK options:

  • --gdk-debug=FLAGS. Gdk debugging flags to set
  • --gdk-no-debug=FLAGS. Gdk debugging flags to unset
  • --gtk-debug=FLAGS. Gtk+ debugging flags to set
  • --gtk-no-debug=FLAGS. Gtk+ debugging flags to unset
  • --gtk-module=MODULE. Load an additional Gtk module
  • -install. Install a private colormap

X11 options:

  • --display=DISPLAY. X display to use
  • --sync. Make X calls synchronous
  • --no-xshm. Don't use X shared memory extension
  • --xim-preedit=STYLE
  • --xim-status=STYLE
  • --g-fatal-warnings. Make all warnings fatal

Ad Hoc

Ad hoc testing is covered by users in the Internet community, as well as casual use.

Regression

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 acceptance testing that occurs during those periods.
  • Ad hoc testing with daily builds.