Plugins/OOPP Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 25: Line 25:
#* especially interested in crashes which don't trigger the Mozilla crash reporter, especially when they are reproducible.
#* especially interested in crashes which don't trigger the Mozilla crash reporter, especially when they are reproducible.


== Filing OOPP Bugs ==
== OOPP Bugs! ==
# Check for bugs
# Check the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 known OOPP bug] list first!
#* Is there a bug listed [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 here] already?  If so, comment!
# If not, open one in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core bugzilla!].  Apply the following:
#* If not, open one in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core bugzilla!].  Apply the following:
#* select Core::Plugins component
#** select Core::Plugins component
#* Add '''[OOPP]''' in the title
#** Add '''[OOPP]''' in the title
#* Add '''[OOPPTestday]''' in the Whiteboard
#** Add '''[OOPPTestday]''' in the Whiteboard
#* Add '''478976''' to the ''Blocks:'' field so it gets picked up in the dependency list.
#** Add '''478976''' to the ''Blocks:'' field so it gets picked up in the dependency list.


== Resources ==
== Resources ==

Revision as of 01:34, 4 February 2010

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

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. Test a few popular plugin sites:
  2. 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:
    • 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