Plugins/OOPP Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Testing OOPP: Silverlight.com is not the site you want.)
No edit summary
 
(42 intermediate revisions by 9 users not shown)
Line 1: Line 1:
A guide to test the newly added Out-Of-Process-Plugins in the Mozilla Nightly builds.   
A guide to test the newly added Out-Of-Process-Plugins in the Mozilla Nightly builds.   
== Status ==
Week of May 21st: Stable


== Setup ==
== Setup ==
# Download the latest Trunk build from http://nightly.mozilla.org
# Download the latest Trunk build from [http://nightly.mozilla.org nightly.mozilla.org]
#* Note: Must be [[linux]] or [[Windows]] 32-bit builds
#* Note: Must be Linux or Windows 32-bit builds
# After installing the build, verify the following preference value is enabled in about:config '''dom.ipc.plugins.enabled = true'''
# After installing the build, verify the following preference value is enabled in about:config '''dom.ipc.plugins.enabled = true'''
# Have at least one of the recommended plugins installed (Flash, Java, Quicktime, and Silverlight)
# Have at least one of the recommended plugins installed (Flash, Java, Quicktime, and Silverlight)
Line 9: Line 12:
# Run your Process monitor of choice. (eg. Task Manager, Process Explorer for Windows, Pioneer Explorer, top command on Linux)
# Run your Process monitor of choice. (eg. Task Manager, Process Explorer for Windows, Pioneer Explorer, top command on Linux)


== Testing OOPP ==  
== Testing OOPP ==
# Install a few plugins:
#* Flash
#* Silverlight (or [http://www.go-mono.com/moonlight/ Moonlight] for Linux Users)
#* Java
#* Quicktime
#* Quakelive
#* [https://wiki.mozilla.org/QA/Plugins Extended List of Plugins]
# Test a few popular plugin sites:
# Test a few popular plugin sites:
#* [http://bubblemark.com/ Bubblemark demos] - Silverlight 1.1, 2, 3 samples.
#* [http://www.beatport.com Beatport]
#* [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.net/showcase Silverlight]
#* [http://www.bing.com/videos/browse?FORM=Z9LH5 Bing Videos]
#* [http://www.silverlight.net/showcase Silverlight Showcase]
#* [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]
#* Full flash sites like [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water]
#** 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]
#* Full flash sites: [http://www.gotmilk.com Gotmilk?], [http://www.vitaminwater.com/ Vitamin Water], [http://www.grooveshark.com Grooveshark]
#* 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 out for:
# Look out for:
Line 24: Line 40:
#* 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 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.
#* especially interested in crashes which don't trigger the Mozilla crash reporter, especially when they are reproducible.
# Check for bugs
 
#* Is there a bug listed [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 here] already?  If so, comment!
== Plugin Crashed UI ==
#* If not, open one in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core bugzilla!]
* Verify the Plugin Crashed UI images displayed after crashing, and submitting a report.
#* use Core::Plugins component
[[File:PluginCrashNotification.png|700]]
 
== OOPP Bugs! ==
# Check the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 known OOPP bug] list first!
# If not, open one in [https://bugzilla.mozilla.org/enter_bug.cgi?&blocked=478976&product=Core&short_desc=%5BOOPP%5D&status_whiteboard=%5BOOPPTestday%5D&version=Trunk 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 '''[OOPP]''' in the title
#* 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 ==
* [http://blog.mozilla.com/dolske/2010/02/10/crashed-plugin-ui/ Crashed Plugin UI]
* [https://wiki.mozilla.org/QA/Plugins Extended List of Plugins]
* List of [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 known bugs]
* List of [https://bugzilla.mozilla.org/showdependencytree.cgi?id=OOPP&hide_resolved=1 known bugs]
* [http://wiki.mozilla.org/Plugins/OOPP_Testing/ArchivesPlugins/OOPP_Testing/Archives Initial Testplan Draft] (bsmedberg)
* [http://wiki.mozilla.org/Plugins/OOPP_Testing/ArchivesPlugins/OOPP_Testing/Archives Initial Testplan Draft] (bsmedberg)
* Electrolysis [https://wiki.mozilla.org/Electrolysis/Meetings Weekly Updates]
* Electrolysis [https://wiki.mozilla.org/Electrolysis/Meetings Weekly Updates]
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=product;type0-0-1=substring;field0-0-1=component;value0-0-2=OOPPTestday;type0-0-3=substring;query_format=advanced;value0-0-3=OOPPTestday;field0-0-3=status_whiteboard;field0-0-2=short_desc;value0-0-1=OOPPTestday;type0-0-0=substring;value0-0-0=OOPPTestday;type0-0-2=substring Bugs filed] during testday
== Manually Killing the Runtime Process/Report Submission ==
If you manually kill the mozilla-runtime process, there is no crash, so it's expected that it says "No report available".
All Flash instances live in a single process. If a particular page causes flash to crash, all the tabs with Flash in them will show the plugin-crash UI. After you submit the report, the other tabs shouldn't have a "please submit report" link any more (because you already submitted it in the first tab).
== Related Bugs to OOPP ==
* Fixed [http://bit.ly/fixedOOPP OOPP buglist]
''Updated on Mar 15th, 2010
* '''META''' {{Bug|478976}} - (OOPP) Electrolysis + plugins tracking
** [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
* '''META, FIXED''' {{Bug|538910}} - Plugins: Need a "plugin crashed" UI
** [https://bugzilla.mozilla.org/showdependencytree.cgi?id=538910&hide_resolved=1 Dependency Tree]
* '''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
== Mac OS Versions not supported ==
*Mac 10.5 will not be supported per {{bug|571135#c15}}

Latest revision as of 00:27, 31 July 2010

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

Status

Week of May 21st: Stable

Setup

  1. Download the latest Trunk build from nightly.mozilla.org
    • Note: Must be Linux or Windows 32-bit builds
  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.

Plugin Crashed UI

  • Verify the Plugin Crashed UI images displayed after crashing, and submitting a report.

700

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

Manually Killing the Runtime Process/Report Submission

If you manually kill the mozilla-runtime process, there is no crash, so it's expected that it says "No report available".

All Flash instances live in a single process. If a particular page causes flash to crash, all the tabs with Flash in them will show the plugin-crash UI. After you submit the report, the other tabs shouldn't have a "please submit report" link any more (because you already submitted it in the first tab).

Related Bugs to OOPP

Updated on Mar 15th, 2010

Mac OS Versions not supported

Retrieved from "https://wiki.allizom.org/index.php?title=Plugins/OOPP_Testing&oldid=242271"