Plugins/OOPP Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 10: Line 10:
== Testing OOPP ==  
== Testing OOPP ==  
# Test a few popular plugin sites:
# Test a few popular plugin sites:
* [http://www.youtube.com Youtube]
#* [http://www.youtube.com Youtube]
* [http://www.hulu.com Hulu.com]  
#* [http://www.hulu.com Hulu.com]  
* [http://www.dailymotion.com Dailymotion]
#* [http://www.dailymotion.com Dailymotion]
* [http://www.silverlight.com/showcase Silverlight]
#* [http://www.silverlight.com/showcase Silverlight]
* Play Mafia Wars / Farmville on [http://www.facebook.com Facebook]
#* Play Mafia Wars / Farmville on [http://www.facebook.com Facebook]
* Full flash sites like [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water]
#* Full flash sites like [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water]
* or Pick one of the [https://wiki.mozilla.org/MozillaQualityAssurance:Test_JavaApplets many Java sites].
#* or Pick one of the [https://wiki.mozilla.org/MozillaQualityAssurance:Test_JavaApplets many Java sites].
# Look for crashes, hangs,
# 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 reproducable.
# Check for bugs
#* 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!]
** use Core::Plugins component
** Add '''[OOPP]''' in the title


== Resources ==
== Resources ==

Revision as of 23:59, 29 January 2010

Testing multi-process plugins:

Setup

  1. Download the latest Trunk build from http://nightly.mozilla.org.
  2. Must be linux or windows 32-bit builds
  3. After installing, verify the config value is enabled in about:config dom.ipc.plugins.enabled = true
  4. Have at least one of the recommended plugins installed (Flash, Java, Quicktime, and Silverlight)
  5. 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 reproducable.
  3. Check for bugs
    • Is there a bug listed here already? If so, comment!
    • If not, open one in bugzilla!
    • use Core::Plugins component
    • Add [OOPP] in the title

Resources