Marketing:Thunderbird WebsiteQAPlan

From MozillaWiki
Jump to: navigation, search

Description of Release


Begin testing: 2/13/09
Finish testing as much as possible: 2/18/09
Absolutely must be ready to ship by: 2/25/09

Implementation Bug / Bugs Fixed

Test Plan

General Markup Testing

  1. W3C Markup Validation Service online test
    1. (Does CSS/XHTML, etc.)
  2. Broken link checker online test

Accessibility Testing

  1. Cynthia online test
  2. Watchfire WebXACT online test
  3. TAW online test

Browser Testing Matrix

Windows XP SP2 Windows Vista Mac Linux
Firefox 3.0.6 P1 P1 P1 P1
Internet Explorer 7 P1 P1 N/A N/A
Internet Explorer 6 P1 N/A N/A N/A
Chrome P2 P2 P2 P2
Safari 2.0.4 / 3.2 P2 P2 P1 N/A

Test Results (Matrix)

Windows XP SP2 Windows Vista Mac Linux
Firefox 3.0.6 . . . .
Internet Explorer 7 . . N/A N/A
Internet Explorer 6 . N/A N/A N/A
Chrome . . . .
Safari 2.0.4 / 3.2 . . . .

Detailed Test Results

What to test:

  1. Run through the pages for each available/completed locale
  2. Make sure that the pages look OK in Right To Left languages, which are:
    1. he, ar, fa
  3. Make sure that if we display a Download Now box somewhere, the box is big enough for the translated text
  4. If we have a screenshot, see if it makes sense to have it localized (Thunderbird interface and web page displayed)
    1. Tier one locales should have:
      1. Localized text
      2. Localized websites in the screenshot
      3. Worry about seeing Windows Vista screenshots primarily, but check for Mac screenshots on the tier 1 locales
    2. Tier two locales:
      1. To prioritize, ensure that their whatsnew pages are localized first
    3. Tier three locales:
      1. Best effort, as time allows
  5. See if all links work correctly, we often provide redirects to Mozilla Europe/Japan/China for pages like the release notes
  6. Testing of any locale fallback mechanism we put on the pages, make sure that we do not send people to non-translated resources if we have a translated one
  7. Ensure XHTML Strict 1.0 validation
    1. W3C validator
  8. Localized page titles


How to substitute:

Reporting / Bug Tracking

Tracking bug -

KNOWN ISSUES (no need to report):

When a page passes

  • Google Doc
  • Mark it by turning its cell color green for the particular page/locale

How to file a bug


List of Locales

Tier 1 (to get us started):

Page-localization status:

L10n specific checklist

  • check that the page title (that appears in the title bar is translated)
  • check that if the page has a 'meta description' tag, it is translated
  • check that pages are in utf8
  • check that the header/footer are translated, they pick strings from the main.lang file
  • check that download box text is translated
  • check that text does not overflow download boxes or other non-fluid parts of the layout
  • for rtl, check that the design is not broken
  • any css/markup fix after localization has started should result in testing localized pages (a couple of ltr locales plus a rtl one). If the design is broken, it should be fixed by the web designer or a bug filed
  • for tier1 locales, check that we have localized screenshots
  • make sure that if we support a locale on, redirects users of this language to a localized page and not en-US