Releases/Firefox 4b7/Test Plan:Feature Area Testing:Compartments

From MozillaWiki
Jump to: navigation, search

Fx 4b7 Test Plan

Compartments Testing (pre beta 7)

We'll track compartments (GC) testing here. Focus on functionality where there's interaction between chrome and content. Some of the add-ons of interest are: Firebug, Greasemonkey, AdBlock, Mozmill, Selenium.

Is AdBlock really blocking? I think there is a problem still (error in the console). [gal]

Testing Matrix (lastest build)

As of 10/05 @ 9:30am (might change often):

WinXP Mac OS Linux
Firebug 1.6xb1 X (crash, manually)
X (crash on startup, Firebug Team test suite)
OK (manual spot check) - retesting now X (Can't use it. No submenus.)
Greasemonkey OK (manual spot check) OK (manual spot check)
Adblock X (crasher, fixed this evening) X (crasher, fixed) X (crasher, fixed)
Mozmill X (unable to run) X (unable to run) X (unable to run)
Selenium X (unable to install) X (unable to run) X (unable to run)
Web Console
Other (google toolbar?)...

Results Notes

First Tryserver Build

  • XP
    • Firebug:
      • Steps: Open Firebug (F12), select the Script panel, use the mini options menu and pick Enable, refresh the page (Firebug disappears), press F12: Crash
      • On start-up: error messages like: Error: uncaught exception: [Exception... "Component returned failure code: 0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS) [nsIXPCComponents_Utils.lookupMethod]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://greasemonkey/content/utils.js :: GM_listen :: line 42" data: no]
      • Using first tryserver build and Firebug 1.6b1
  • Mac
  • Linux
    • Firebug:
      • After installing Firebug you can go to that menu, but it doesn't expand, so you can't use it.

Web Sites Spot Checks

In addition to spot checking the add-ons above, we'll check a few popular web sites looking for obvious, major problems.

  • Google: gmail, docs, picassa
  • Twitter
  • Yahoo!
  • Amazon
  • Facebook
  • ...

Reference