Plugins/OOPP Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 62: Line 62:
** [https://bugzilla.mozilla.org/showdependencytree.cgi?id=478976&hide_resolved=1 Dependency Tree]  
** [https://bugzilla.mozilla.org/showdependencytree.cgi?id=478976&hide_resolved=1 Dependency Tree]  
* '''BRANCH''' {{Bug|539055}} - (LorentzBeta1) Tracking release of Firefox Lorentz Beta 1 with OOPP
* '''BRANCH''' {{Bug|539055}} - (LorentzBeta1) Tracking release of Firefox Lorentz Beta 1 with OOPP
* '''FIXED''' {{Bug|538910}} - Plugins: Need a "plugin crashed" UI
* '''META, FIXED''' {{Bug|538910}} - Plugins: Need a "plugin crashed" UI
* '''NEW''' {{Bug|550293}} - Tweak visual style of crash-reporter UI
* '''NEW''' {{Bug|550293}} - Tweak visual style of crash-reporter UI
* '''NEW''' {{Bug|550303}} - plugin-crashed UI needs more user opt-in
* '''NEW''' {{Bug|550303}} - Update crash-reporter UI and tweak visual style
* '''NEW''' {{Bug|550293}} - plugin-crashed UI needs more user opt-in

Revision as of 20:21, 15 March 2010

A guide to test the newly added Out-Of-Process-Plugins in the Mozilla Nightly builds.

Status

Week of March 8th: stable?

Setup

  1. Download the latest Trunk build from http://nightly.mozilla.org
  2. After installing the build, verify the following preference value is enabled in about:config dom.ipc.plugins.enabled = true
  3. Have at least one of the recommended plugins installed (Flash, Java, Quicktime, and Silverlight)
    • Note: because Flash 10.1 beta eats crash reports, we want to focus testing on 10.0.
  4. Run your Process monitor of choice. (eg. Task Manager, Process Explorer for Windows, Pioneer Explorer, top command on Linux)

Testing OOPP

  1. Install a few plugins:
  2. Test a few popular plugin sites:
  3. Look out for:
    • Crashes
    • Hangs
    • incorrect display/audio/interaction
    • especially on Windows, any feature which may pop up dialog boxes or system prompts (known cause of hangs), or use the window system in unusual ways (full-screen)
    • especially interested in crashes which don't trigger the Mozilla crash reporter, especially when they are reproducible.

OOPP Bugs!

  1. Check the known OOPP bug list first!
  2. If not, open one in bugzilla!. Apply the following (this is done automatically if you use the link back there):
    • select Core::Plugins component
    • Add [OOPP] in the title
    • Add [OOPPTestday] in the Whiteboard
    • Add 478976 to the Blocks: field so it gets picked up in the dependency list.

Resources

Related Bugs to OOPP

Updated on Mar 9th, 2010

  • META bug 478976 - (OOPP) Electrolysis + plugins tracking
  • BRANCH bug 539055 - (LorentzBeta1) Tracking release of Firefox Lorentz Beta 1 with OOPP
  • META, FIXED bug 538910 - Plugins: Need a "plugin crashed" UI
  • NEW bug 550293 - Tweak visual style of crash-reporter UI
  • NEW bug 550303 - Update crash-reporter UI and tweak visual style
  • NEW bug 550293 - plugin-crashed UI needs more user opt-in