QA/Execution/Web Testing/Mozilla.com/Tips and Pointers

Mozilla.com has a three-tier system:

• trunk
• staging
• production

Fixes are usually checked into SVN, and trunk pulls from SVN almost instantaneously; once changes are tested and verified, they can be pushed to staging; alternatively, they can be pushed to both staging and production if need be.

Relationship of What's New & First Run pages

• Freshly installed Firefox, you get:
  • First Run (left tab focused/active)
  • Firefox start page on Google.com (right tab)
• 3.0.x -> 3.5.x, you get:
  • First Run (left tab)
  • What's New (right tab focused/active)
• 3.0.x-1 (next-to-latest version) -> 3.0.x (latest version)
  • Firefox start page on Google.com (left tab)
  • What's New page (right focused/active)

Redirects / user-agent detection

• Redirects:
  • Most redirects happen in .htaccess (302s, usually)
• User-agent detection:
  • Usually uses RewriteCond rules

Download.html

• FULL (takes product, OS, lang parameters): http://www.mozilla.com/en-US/products/download.html?product=firefox-3.5&os=osx&lang=en-US
• FLAT (if anything is missing you, such as http://www.mozilla.com/en-US/products/download.html?product=firefox-3.5, you get a "flat" page with links to all platform builds

Video pages

• Pages with video should be checked with Flash -and- OGG-capable browsers (with fallback in most cases)
  • e.g. http://www.mozilla.com/en-US/firefox/video/