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 test cases > Test documentation for toplevel Navigator menus

Testing Toplevel Navigator Menus

Maintained by: Sarah Liberman

This test document covers the functionality of the menus off of the main menubar within the web browser (Navigator). Context menus are covered separately by the Navigator context menu test document.

Will test

Testing should cover these areas:

  • Cross-platform consistency, namely between the Linux/unix and Win32 products.
  • Native Mac OS menu behavior.
  • Style, spelling, grammar, etc., of the content in menus.
  • Overall functionality, to the extent that a given menu item should bring up the expected feature.

Will NOT test

The following areas will not be covered. Please refer to the appropriate test plan for further information:

  • Keyboard accelerators and menu access keys: While defined within the Menu UI specification, testing is really covered under keyboard navigation --with the exception of labelling issues such as access key redundancy or garbled accelerators.
  • Menu items that appear in apps other than the browser window (due to time constraints), such as
    • Composer (Editor)
    • Mail & News
    • Mail compose window
    • Address Book
    • Instant Messenger
    • IRC Chat (Chatzilla)
    • other Mozilla or Netscape add-on applications
  • Menu functionality testing is for the most part just limited to access to these features. The underlying behavior/details is covered by other QA areas/test documentation. These include, but are not limited to:
    • Opening web locations (surfing) or files; opening/closing browser windows
    • Saving files
    • Sidebar
    • Editor-oriented tasks
    • Sending mail
    • Offline feature
    • Printing
    • Stylesheets
    • Themes
    • Page source or info
    • History (Back, Forward)
    • Networking (Reload, Stop)
    • Searching the web, or searching within a webpage
    • Bookmarks
    • Translation, Character Sets
    • Functionality of the Tasks and Tool items (Java console, JavaScript console, etc.)
    • Form Manager features
    • Help content
    • Toolbars, Taskbar, and other windowing controls

Issues, references & bug information

The UI specification for toplevel menus is at http://mozilla.org/mailnews/specs/proposals/MenuFrame.html. This document also includes accelerators (hotkeys) and menu access keys.

Differences between Mozilla and Netscape : There are some differences between their toplevel Navigator menus, namely:

  • Netscape-only:
    • File > Print Plus:
      • Print Central
      • Printer Supplies
      • Printing Services
    • Tools > Search submenu:
      • 6 predefined search engine/reference links
      • Internet Keywords
    • Window menu:
      • Instant Messenger
    • Net2Phone: Win32-only
    • Help menu:
      • Help and Support Center
      • What's New in Netscape <version>?
      • Feedback Center
      • Security Center
      • About Netscape <version>
  • Mozilla-only:
    • Window > IRC Chat
    • Tools > Web Development submenu:
      • JavaScript Debugger
      • DOM Inspector
    • Tools > Image Manager
    • Debug and QA toplevel menus are always present
    • Help menu:
      • Help Contents
      • Release Notes
      • About Mozilla

Since this is a high-visibility area for Mozilla and Netscape, there's a good chance that problems you see with menus might already exist as reported bugs (or even fixed).

Typical Bugzilla components would include:

  • XP Toolkit/Widgets: Menus: Infrastructure.
  • XP Apps: GUI Feature: Issues with the content of menu items (eg, typos, labels, etc.), as well as functionality of (some of) the applications accessed from the menus.

The XP Toolkit/Widgets: Menus component (aka, XP Menus) is for bugs relating to the behavior/functionality (infrastructure) of the menus themselves, not the applications that can be accessed from them. If there are problems with the functionality of the accessed applications, those bugs go to their appropriate component. For example, if you couldn't access the Bookmarks editor from the Bookmarks menu, that'd be assigned to the Bookmarks component, rather than XP Toolkit/Widget: Menus.

On the other hand, the XP Apps: GUI Features component tends to be a general basket for many problems, so sometimes a bug filed here will be reassigned to a more appropriate component. We are currently investigating reorganization of the XPApps components (see bug 68621 ). In the meantime, check out the Who to bug in Navigator page for some tips.

You might also want to check out the Frequent Bugs List, as well as the following Bugzilla queries.

Important: Because these queries are based solely on the XP Toolkit/Widgets: Menus component, they'll also include bugs for context menus. In addition, to find bugs concerning menu content, you might need to run separate queries (especially under the XP Apps component).

Test coverage & outline

Test coverage will occur on several levels:

  1. Acceptance tests (breadth of functionality)
  2. Functional tests, including unit tests (depth of functionality)
  3. Stress, boundary and negative and other comprehensive-level tests (where applicable and when possible)
  4. Ad hoc testing
  5. Regression testing
  6. ? Automation ?

Acceptance tests

Basically ensure the following:

  • Expected menu items exist (or are disabled given particular milestones)
  • Able to pull down and dismiss menus and submenus
  • Able to read and select menu items
  • Keyboard access to menubar. The following shortcuts focus the menubar so that you can use either access keys or arrow keys to maneuver through the menus.
    • Win32 and Unix: Either Alt or F10 will focus the menubar (the File item in particular).
    • Mac OS X: If full keyboard access is turned on, the default shortcut would be Control+M if letter shortcuts are used, or Control+F2 if function keys are used. This will focus the menubar at the Apple menu. Since access keys aren't implemented on Mac OS, you can only use the arrow keys to move through menus.
    • The Esc key should dismiss menus. If a submenu is expanded, then Esc would collapse that expanded flyout, returning to the parent menu listing.

Functional tests

As noted above, the actual functionality of many applications accessed via menus is covered by other components. Below I've denoted the Bugzilla components which should be used for application problems. All are in the Browser product unless otherwise noted.

  • Overall behavior & appearance (infrastructure affecting all menus)
    • Look and feel/appearance (eg, opacity, flickering), consistency across platforms: captions, shortcut labels (keyboard accelerators), access keys (mnemonics), separators, order of menu items.
    • Menu content: spelling, typos, grammar, punctuation.
    • Behavior of hierarchical and nonhierarchical menus.
    • Note which are greyed out and which aren't, as appropriate.
    • Selection and cancellation of menu items.
    • Any focus effects.
  • File menu
    • New
      • Navigator Window. Opens another browser window. Bugs go to XP Apps: GUI Features.
      • Navigator Tab. Opens a tabbed browser within the current Navigator window. Bugs go to Tabbed Browser.
      • Message. Opens new Mail compose window. Bugs go to the Mail Window Front End component of the MailNews product.
      • Address Book Card. Opens new Address Book Card window. Bugs go to the Address Book component in the MailNews product.
      • Blank Page to Edit. Opens a new editor window. Bugs go to Editor: Composer.
      • Instant Message. (Netscape) Opens new Instant Messenger compose window. Bugs should be filed in the Instant Messenger product of Bugscape.
    • Open Web Location... Open Web Location dialog appears. Bugs go to XP Apps: GUI Features.
    • Open File... Open File dialog, aka, the file picker appears. Bugs go to XP Apps: GUI Features.
    • Close Tab. Closes current tabbed browser. If there's only one window, then this should quit Mozilla or Netscape entirely, except on Mac OS, where the menubar persists and is partially active; see the Mac OS section for more details. Bugs should go to Tabbed Browser.
    • Close (or Close Window with tabbed browser). Closes current window. If there's only one window, then this should quit Mozilla or Netscape entirely, except on Mac OS, where the menubar persists and is partially active; see the Mac OS section for more details. Bugs should go to Tabbed Browser if the tabbed UI is involved, or XP Apps.
    • Save Page As... Save file picker dialog appears. Bugs go to File Handling.
    • Save Frame As... (Framed web pages) Save file picker dialog appears. Bugs go to File Handling. Note: Focus needs to be in a given frame for this item to appear. By default, focus is in the frameset document (not in any given frame) when such a page is loaded, so this item won't initially appear in the File menu. See bugs 122505, 89975 and 56540 for details.
    • Send Page. Brings up Mail compose window that includes the current page's URL as well as the page itself as an attachment. Bugs go to the Composition component of the MailNews product.
    • Send Link. Brings up Mail compose window that includes only the current page's URL. Bugs go to the Composition component of the MailNews product.
    • Edit Page. Brings up current page in an editor window. Bugs go to Editor: Composer.
    • Page Setup. Brings up Page Setup dialog (native on Win32 and Mac OS; XUL version on Unix). Bugs belong in Printing.
    • Print Preview. This changes the current browser window to display the content in print format mode. Bugs belong in Print Preview.
    • Print... Brings up the print dialog
    • (native on Win32 and Mac OS; XUL version on Unix). Bugs go toPrinting.
    • Print Plus. (Netscape) Issues here should go somewhere in Bugscape.
      • Print Central. Loads Print Central URL in Netcenter.
      • Printer Supplies. Loads printer supply URL in Netcenter.
      • Printing Services. Loads Printing Services URL in Netcenter.
    • Work Offline. Toggles between turning network connectivity on and off throughout Mozilla or Netscape. Issues should be filed in the Offline component of the MailNewsproduct.
    • Quit (Exit on Win32). Quits all Mozilla and Netscape products (ie, ends the session). Bugs go to XP Apps.
  • Edit menu
    • Undo. Removes last editor function. Bugs go to Editor: Composer.
    • Redo. Repeats last editor function. Bugs go to Editor: Composer.
    • Cut. Cuts and places selection. Bugs go to Editor: Composer.
    • Copy. Copies and places selection. Bugs go to Editor: Composer.
    • Paste. Pastes selection. Bugs go to Editor: Composer.
    • Delete. Deletes selection. Bugs go to Editor: Composer.
    • Select All. Selects all content in a given frame or page. Bugs go to Selection.
    • Find in This Page... Brings up Find on Page dialog. Bugs go into XP Apps: GUI Features.
    • Find Again. Finds last searched item on current page. Bugs go to XP Apps: GUI Features.
    • Fill in Form. Prefills HTML form fields with saved data. Bugs go Form Manager.
    • Save Form Info. Captures data in the HTML form fields of the current page. Bugs go Form Manager.
    • Preferences... Brings up Preferences dialog. Refer to the Preferences test page for more details. Bugs go to Preferences.
  • View menu
    • Show/Hide submenu. When selected, checkmark appears to the left of the menu item's label. Should be able to toggle between displaying and hiding toolbars in the browser window. Unless otherwise noted, application bugs go to XP Apps: GUI Features.
      • Navigation Toolbar
      • Personal Toolbar. Bugs go to Bookmarks.
      • Site Navigation Bar (Mozilla) submenu
      • Status Bar
      • Component Bar
      • Sidebar (Mozilla), or My Sidebar (Netscape). Bugs go to Sidebar.
    • Full Screen. Converts browser window into full screen mode. Bugs go to XP Apps.
    • Stop. Interrupts page loading. Bugs go to Networking.
    • Reload. Reloads page content. Bugs go to Networking.
    • Show Images. If graphics are displayed as per user prefs, then this should be greyed out. Otherwise, if there aren't graphics, selecting this should display them. Currently not implemented: see bug 57505.
    • Text Size (<percent>%). Resizes the font size of text in the browser content area; use its submenu to select the size. Bugs go to Style System.
    • Use Stylesheet. If available, its submenu will display alternative CSS style sheets to select. Bugs go to Style System.
    • Page Source. Brings up Source window displaying page's code. Application bugs go to View Source.
    • Page Info. Brings up Page Info window. Bugs go to Page Info.
    • Character Coding. Its submenu allows the user to display web pages with a different character set. Bugs go to Internationalization.
    • Apply Theme. Its submenu allows the user to change or download another theme. Bugs go to Themes.
  • Go menu. Bugs go to History: Session.
    • Back. Goes to (loads) previous page in session history.
    • Forward. Goes to (loads) next page in session history.
    • Home. Goes to (loads) user-defined home page.
    • History. Brings up History dialog. Application bugs go to History: Global.
    • <Session URLs>. Goes to (loads) selected page in this list.
  • Tools menu
    • Search the Web. (Mozilla) Redirects user to preset search engine. Bugs go to Search.
    • Search submenu (Netscape).
      • Search the Web. Redirects user to preset search engine. Bugs go to Search.
      • Six predefined search engine/reference links. Bugs go to Search.
      • Internet Keywords. (Netscape) Redirects user to Netcenter page describing Internet keyword use. Bugs go to Search.
    • Form Manager. Bugs here go into the Form Manager component.
    • Fill in Form
    • Save Form Info
    • Edit Form Info
    • Manage Sites
    • Cookie Manager submenu. Its items cover cookie management. Problems with this feature should be filed under the Cookies component.
      • Block Cookies from this Site
      • Unblock Cookies from this Site
      • Manage Stored Cookies
    • Image Manager submenu. (Mozilla) Its items cover image management in web pages. Bugs go to XP Apps: GUI Features.
      • Manage Image Permissions
      • Block Images from this Site
      • Unblock Images from this Site
    • Password Manager submenu. Its items cover management of browser and mail passwords. Problems found with this feature should go under the Password Manager component.
      • Lock Passwords
      • Unlock Passwords
      • Manage Stored Passwords
    • Download Manager. Launches the Download Manager window. Bugs go to Download Manager.
    • Web Development submenu
      • Java Console. Launches the Java console. if Java is installed. Application bugs go to OJI.
      • JavaScript Console. Launches JavaScript console. Bugs go to JavaScript Console.
      • JavaScript Debugger. (Mozilla) Launches the JavaScript Debugger window. Bugs go to JavaScript Debugger.
      • DOM Inspector. (Mozilla) Launches the DOM Inspector window. Bugs go to DOM Inspector.
  • Window menu. Window titles of all application windows in a Mozilla or Netscape session should be listed at the end of this menu.
    • Navigator. Launches another browser window with the user's preset homepage. Bugs go to XP Apps.
    • Mail & Newsgroups. Launches the Mail & News window. Bugs go to the Mail Window Front End component of the MailNews product.
    • Instant Messenger. (Netscape) Launches the Instant Messenger login window. Bugs should be filed in the Instant Messenger product of Bugscape.
    • Composer. Launches an editor window. Bugs go to Editor: Composer.
    • Address Book. Launches the Address Book window. Bugs go to the Address Book component in the MailNews product.
    • IRC Chat. (Mozilla) Launches the Chatzilla window. Bugs go to Chatzilla.
  • Help menu
    • Mozilla-only help items:
      • Help Contents. Launches the Mozilla Help window. Bugs go to the Help component.
      • About Mozilla. Launches another window containing version info. Bugs go to Browser-General.
    • Netscape-only help items:
      • Help and Support Center. Bugs to the Help component. However, if it concerns a Netscape-only feature, then the bug should go into Bugscape.
      • What's New in Netscape <version>? Redirects user to the latest Netcenter splash page. Bugs should go into Bugscape.
      • Feedback Center. Redirects user to the Feedback Center in Netcenter. Bugs should go into Bugscape.
      • Security Center. Redirects user to the Security Center in Netcenter. Bugs should go into Bugscape.
      • About Netscape <version>. Launches another window containing version info. Bugs should go into Bugscape.
    • About Plug-ins. Bugs should go into Plug-ins.
  • Debug (Mozilla, mostly). This contains a bunch of built-in tests.
  • QA (Mozilla, mostly). This contains links to various QA/testing resources.

Mac OS menus

Because the toplevel menus on Mac OS are natively implemented, there are some differences in test coverage, outlined below.

  • Mac OS X menus include an additional Mozilla (or Netscape) toplevel menu:
    • About Mozilla (or About Netscape <version> ). Opens another browser displaying version info.
    • Preferences... This item is here and not in the Edit menu. Opens the Preferences dialog.
    • Services. Not implemented; see bugs 110372 and 104331.
    • Hide Mozilla (or Hide Netscape). Hides Mozilla (or Netscape).
    • Hide Others. Hides other (non-hidden) applications running on the Mac.
    • Show All. Shows all (previously hidden) application running on the Mac.
    • Quit. This item is here and not in the File menu. Quits Mozilla (or Netscape).
  • When there are no open windows, some of the menu items should still be accessible, in either Mac OS X or Mac OS 8/9.
    • Disabled items. Menu items which are incorrectly enabled are tracked by bug 75660.
      • File items:
        • Close
        • Save Page As...
        • Send Page...
        • Send Link...
        • Edit Page
        • Print Preview
      • All Edit menu items, except for Preferenceson Mac OS 8/9
      • All View menu items, except for the Apply Theme items
      • Edit items:
        • Find in this Page...
        • Find Again
      • All Go menu items, except for Home
      • Bookmarks items:
        • Add Bookmark
        • File Bookmark...
    • Enabled items. Essentially the things not listed in the above section. ;-)
      • File > Open File... fails, bug 83313
      • File > Open Web Location... fails, bug 84011
      • Some View > Apply Theme items fail, bug 114967
      • Go > Home fails, bug 83343

Stress, boundary & negative tests, etc.

  • Mac OS: Access when only the menubar is present (no windows open).
  • Large menus (length/tallness of menu), eg, Bookmarks.
    • Menus extending beyond the size of the browser window, or monitor screen.
    • Scrolling menus.
  • Overlapping menus --ie, menus when browser is near screen border.
  • Menus with large hierarchies (child menus, grandchild, great-grandchild, etc.), again Bookmarks
  • Long menu captions (width of menu).
  • Color depth (eg, 1-bit color on Linux) variations.
  • Different monitor resolutions
  • Effects of different themes (Linux, Windows), eg, the High Contrast theme on Windows.
  • Customizing Mac OS menu appearance by changing the desktop font and theme from the appropriate Appearance control panel (Mac OS 8/9) or Personal system preference (Mac OS X).
  • Customizing Linux menu appearance by changing the desktop/window manager theme and/or font.
  • Using multiple monitors. Or, in the case of Linux, multiple virtual desktops.

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.