Plugins/OOPP Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 28: Line 28:
#* [http://www.nbcolympics.com NBC Olympics] (Silverlight)
#* [http://www.nbcolympics.com NBC Olympics] (Silverlight)
#* Play Mafia Wars / Farmville on [http://www.facebook.com Facebook]
#* Play Mafia Wars / Farmville on [http://www.facebook.com Facebook]
#** Note: Best results can be archived when having a big farm with a lot of items on it.
#* Shoot some monsters on [http://www.quakelive.com Quake Live]
#* Shoot some monsters on [http://www.quakelive.com Quake Live]
#* Full flash sites: [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water], [http://www.grooveshark.com Grooveshark]
#* Full flash sites: [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water], [http://www.grooveshark.com Grooveshark]

Revision as of 18:57, 9 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