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 plans > Test plan for some XP Navigator features

Test plan for some cross-platform Navigator features

Maintained by: Patty Mac

Overview

XP Apps is a large hodgepodge of browser applications. As the name implies, these have been developed across the main three platforms (unix, Mac OS and MS Windows). This test plan covers XP Apps features which have a graphical user interface (front-end). The corresponding Bugzilla components are described below.

Important Both of these components get a lot of traffic for many problems. For more information on how to better file bugs and/or search for more appropriate owners, check out the page on Who to Bug in the Navigator group .

  • XP Apps: GUI Features: For problems with cross-platform applications that have a graphical interface.
  • XP Apps: If the problem doesn't fit well into the above component, it can go here. For example, infrastructure bugs in the dialogs of several of the GUI features or bugs in their application logic.
  • Page Info: Bugs for the Page/Frame Info window.

Will Test

Testing should cover these areas:

  • Look and feel: visual consistency within the Navigator applicaton.
  • Style, spelling, grammar, etc.
  • Menu items, dialogs (ie, UI only) relevant to file saving and downloading.
  • Menu items, dialogs and behavior of intrapage searching.
  • Menu items, dialogs and behavior of viewing page source and info.
  • Menu items, dialogs and behavior of opening web locations (URLs) and local files (especially the XUL file picker on Linux/unix). Note exceptions below, however.

Will Not Test

The following areas will not be covered. Please refer to the appropriate test plan 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).

  • The following items, while usually filed under XP Apps: GUI Features component, are not covered by this test plan:
    • Location input field (aka, the URLbar) in the Navigation Toolbar.
    • Functionality of any of the toolbars, such as the Personal Toolbar, Navigation Toolbar, Taskbar.
    • Dialog infrastructure.
  • Search in the following
    • Bookmarks: Bookmarks component.
    • History: History component.
    • Mail, News, Address Book: The appropriate component under the MailNews product.
    • User's computer.
    • Internet: Search component.
  • Lower-level functionality of downloading/saving files (eg, unable to download a file at all). Networking component. How well/poorly downloading works isn't covered here, although the UI should be consistent (which is tested here). For example, this plan doesn't cover how well the following situations work, but what the user sees should be consistent (Save File dialog, Saving File dialog and/or Unknown File Type dialog, where appropriate):
    • Downloading binaries/archives (zip, exe, tar, gz, sit); saving images (gif, jpg).
    • Downloading from ftp pages vs http pages.
    • Downloading controlled/influenced by JavaScript, Java, cgi.
  • How skins are applied: either Themes (appearance) or Skinability (changing themes).
  • The Cookie Manager: Cookies component.
  • The Image Manager.
  • Functionality (on a deep level) of opening local files (aka, using file pickers). Since each platform utilizes a native file open application, it would be beyond the scope of testing here. However, how the browser accesses the file picker would be tested.
  • How any of the features listed under "Will Test" behave within apps other than the browser, such as
    • Composer: Editor: Composer component.
    • Mail and News: The appropriate component under the MailNews product.
    • Instant Messenger (only in the commercial Netscape product).
    • IRC (Chatzilla), only in Mozilla. Chatzilla component.
    • etc.

Major Issues & Bug Information

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

Here are some relevant Bugzilla links. FYI: Some of the features described in this plan may or may not be listed under the XP Apps component, so if you don't find what you're looking for here, you may need to do a query which covers other components/parameters. Conversely, some bugs from features not covered by this plan might show up in the queries below.

Test Coverage

XP Apps test areas:

Open Web Location

The Open Web Location dialog allows you to access and edit web pages and files.

Go directly to the test case matrix.

  1. Acceptance level testing:
    • Access to opening web locations.
      • From the main menu: File > Open Web Location
      • Shortcuts: Command/Control/Alt+L for the keyboard accelerator; also keyboard mnemonics (access keys) from File and context menus.
      • From context menus: Open Link in New Window, Open Frame in New Window.
    • Overall appearance
      • Look and feel/appearance, highlighting, modality: menu items, Open Web Location dialog (cross-platform).
      • Spelling, typos, grammar of any text/descriptions.
  2. Functional testing:
    • URLs with http, ftp, telnet, gopher, wais, file, JavaScript protocols.
    • URL without protocol specified.
    • URLs to different file types: html, text, xml, binaries/archives, images, pages w/plugin content, pages which would call local applications; files without extensions.
    • URLs with and without fully resolved domain info (intranet vs Internet).
    • URL containing form info.
    • Cutting URLs from and pasting into dialog.
    • Open Web Location dialog features:
      • Web location input field.
      • Choose File button: opens native Open File dialog.
      • 3 radio buttons to choose opening in Current Navigator window, a New Navigator window, or a New Composer window.
      • Open button.
      • Cancel button.
      • Close widget.
  3. Stress, boundary, negative testing:
    • Really long URLs.
    • URLs with invalid characters, whitespace, etc.
    • Opening URLs in multiple Navigator windows...?

Opening local files

As its name implies, the Open File dialog allows you to open files -- namely on your local system and network drives.

Go directly to the test case matrix.

  • Access to opening files locally:
    • From the main menu: File > Open File.
    • From shortcuts: accelerated keyboard shortcut is Command/Control/Alt+O; mnemonic only from File menu.
  • Overall appearance
    • Look and feel: menu item appearance, Open File (native) dialog, which varies from platform to platform.
    • Spelling, typos, grammar of any text/descriptions.
  • See related functional test coverage for Saving/Downloading and Open Web Location above.

Find on Page

The Find on Page dialog allows you to search for strings within the currently viewed web page.

Go directly to the test case matrix.

  1. Acceptance level testing:
    • Access to Find on Page feature
      • From the main menu: Search > Find on this Page, Search > Find Again.
      • Keyboard accelerators: Alt/Command/Control+F for Find, Alt/Command/Control+G for Find Again.
      • Keyboard mnemonics (access keys) from the main menu.
    • Overall appearance
      • Look and feel/appearance, highlighting, modality: menu items, Find in File dialog (cross-platform).
      • Spelling, typos, grammar of any text/descriptions.
  2. Functional testing:
    • Starting Find in various parts of a page or frame (top, middle, bottom).
    • Find in different file types: text, xml, ftp pages.
    • Find in Page Source window.
    • Find with and without case sensitivity.
    • Find with and without document wrapping.
    • Find forwards and backwards.
    • Find using short or long strings.
    • Find using null.
    • Find using only whitespace.
    • Find using prepended/appended whitespace.
    • Find Again.
    • Going between Find on Page and Find Again.
    • Find on Page dialog:
      • Find Text input field.
      • 3 checkboxes for Case Sensitive, Wrap and Backwards.
      • Find button.
      • Cancel button.
      • Close widget.
  3. Stress, boundary, negative testing:
    • Find with really long strings.
    • Find with unusual characters.
    • Find in big pages.
    • Rapid/frequent Find Again's.
    • Interrupting Find (possible?).
    • Multiple Finds.

Page Source

Page Source allows you to view the source code (HTML, JavaScript, etc.) of the currently viewed web page.

Go directly to the test case matrix.

  1. Acceptance level testing:
    • Access to Page Source:
      • From menu, View > Page Source, View > Frame Source.
      • Keyboard mnemonics (access keys) and accelerated keyboard shortcuts.
      • From context menus: View Page Source, View Frame Source.
    • Overall appearance
      • Look and feel/appearance, highlighting/coloring, modality: menu items, Page Source window.
      • Spelling, typos, grammar of any text/descriptions.
  2. Functional testing:
    • View source for a page, frame, frameset.
    • View source for ftp sites/pages.
    • Page Source window has:
      • Titlebar, menubar, statusbar and Taskbar as in a Navigator window.
      • Lacks the Personal and Navigation Toolbars.
    • Color coding in Page Source window (need to compare on different platforms; get final spec here):
      • Regular content text is black.
      • Tags and attribute names are purple; <> are black and the / in closing tags is bold black.
      • Values for tags and attributes, including the quotes, are in blue. = is in black.
      • HTML comments are entirely in green; comments in JavaScript are still black.
      • Entities are in red.
    • Scrolling up and down, left to right: either by thumb or with keyboard (spacebar, PgUp, PgDn, arrow keys). On a related note, other window keyboard accelerators should work, eg, Ctrl+W to close the window.
    • Resize, maximize, minimize source window.
    • Select, copy from source window.
  3. Stress, boundary, negative testing:
    • View source for different file types: text, xml, binaries/archives, images, pages w/plugin content, pages which would call local applications; files without extensions.
    • Open many Page Source windows.
    • Tiny source window.
    • Attempt to cut from or paste to source window.

Page/Frame Info

The Page/Frame Info window allows you to view information on the content in a page or active frame, including image and form information.

Go directly to the test case matrix.

  1. Acceptance level testing
    • Access to Page Info:
      • From menu, View > Page Info. View > Frame has not yet been implemented in the top-level menu.
      • Keyboard mnemonics (access keys) and accelerated keyboard shortcuts.
    • Overall appearance
      • Look and feel/appearance, highlighting/coloring, modality: menu items, Page Info window.
      • Spelling, typos, grammar of any text/descriptions.
  2. Functional testing:
    • View info for a page, frame, frameset.
    • View info for ftp sites/pages.
    • Page Info window has three sections:
      • Information on the current page:
        • Title
        • URL
        • Last modified date
      • Forms on the current page:
        • Form action
        • Method
        • Name
      • Images on the current page:
        • Image URL
        • Width
        • Height
        • Alt text
      • Moveable grippy, below which selected images are displayed.
    • Navigation:
      • Resize, maximize, minimize info window.
      • Scrollability and selection in any of the three sections.
    • Select, copy from info window.
  3. Stress, boundary, negative testing:
    • Open many Page Info windows.
    • View info for different file types: text, xml, binaries/archives, images, pages w/plugin content, pages which would call local applications; files without extensions.
    • Tiny source window.
    • Attempt to cut from or paste to source window.

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.

References

As of this writing, there are not any UI or recent engineering specifications for most of these features.