QA/Execution/Web Testing/PluginCheck: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(35 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Overview==
==Overview==
* Project homepage: https://wiki.mozilla.org/Plugins:PluginCheck/CrossBrowserRelease (slightly outdated, but still useful)


==Timeline/Milestones==
==Bug Lists==
* Testing starts: 3/12/2010
* [https://bugzilla.mozilla.org/buglist.cgi?classification=Other&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=plugins.mozilla.org&product=Websites Open bugs]
* Tentative ship date: 3/18/2010
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&classification=Other&query_format=advanced&bug_status=RESOLVED&component=plugins.mozilla.org&product=Websites fixed bugs] -- note that this list includes PFS and Plugin Directory bugs, too, and is mainly for code updates
** Once we have Firefox.com in production, we should talk about re-organizing the Bugzilla workflow to be clearer which bugs are specifically for Plugin Check


==Open Bugs==
==Found a Bug?==
[http://tinyurl.com/yjqyo2a]
* Help us, please!  File in the [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites"websites"] component, product: plugins.mozilla.org, and in the whiteboard field, enter "0.6.0" (without the quotes).


==Fixed Bugs to Verify==
Thanks!
* [http://tinyurl.com/yzrnoxm]


==Staging Server==
==QA/Dev Process==
* [https://www-trunk.stage.mozilla.com https://www-trunk.stage.mozilla.com]
 
# Dev fixes a bug/finishes a page by marking as "resolved fixed", adds the "qawanted" keyword
# QA checks,approves by adding the comment "qa-verified-trunk" and removes qawanted keyword, if not QA re-opens bug and also removes qawanted keyword.
# '''If the bug is ready to be pushed to production''', anyone can add "push-needed" keyword. '''If the bug is waiting on a particular launch date, don't add this'''
# Dev pushes to production by leaving comment with revision number, removes "push-needed" keyword from bugs that have them
# QA checks on production, marks "verified fixed"


==Supported Browsers==
==Supported Browsers==
* Internet Explorer 8
* Internet Explorer 8, 9 (when it comes out from beta)
* Chrome on Windows, Mac and Windows
* Chrome on Windows, Mac (latest version)
* Opera on Windows, Mac
* Opera on Windows, Mac (latest version)
* Firefox 3.0, 3.5, 3.6
* Firefox 3.0, 3.5, 3.6, 4.0
* Safari 4
* Safari 5 on Mac, Windows


==Supported Plugins==
==Supported Plugins==
* Adobe Flash
*Adobe Flash
* Microsoft Silverlight
* Divx Web Player
* Java Embedding Plugin
* Acrobat Reader
*MoveNetworks Quantum Media Player ( used for videos on ESPN360.com and other major video streaming websites)
*Adobe Reader Plugin
*Adobe Reader Plugin
*Microsoft Silverlight
*Divx Web Player
*Java Embedding Plugin
*Acrobat Reader
*MoveNetworks Quantum Media Player (used for videos on ESPN360.com and other major video streaming websites)
*Quicktime
*Quicktime
*BrowserPlus Plugin
==Positive Test Cases==
1. Load https://www-trunk.stage.mozilla.com/plugincheck with any of the above supported browsers, using the most recent version of each supported plugin<br>
2. Verify that those plugins have their version # in their "Status", and have a green "Up-to-Date" button, which links to their homepage
1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with an *outdated* version of the plugin (oldversion.com is a great resource for Win32.)<br>
2. Verify that we detect the plugin as out-of-date, list its "Status" as "Outdated Version", and have a yellow "Update" button that links to its homepage
1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with a vulnerable version of the plugin (oldversion.com is a great resource for Win32.)<br>
2. Verify that we detect the plugins as vulnerable, and link the user, via an orange "! Update Now" button, to the plugin vendor's homepage
1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with an unknown plugin<br>
2. Verify that we detect the plugin as "Unknown Plugin" in its "Status", and link the user, via a Google search (e.g. http://www.google.com/search?q=current%20version%20plugin%20iTunes%20Application%20Detector) for that plugin
==Staging Server==
* [https://www-trunk.stage.mozilla.com https://www-trunk.stage.mozilla.com]


==Links to Useful Resources==
==Links to Useful Resources==
* [http://www.oldversion.com Oldversion.com] to download old versions of  Windows plug-ins
* [http://www.oldversion.com Oldversion.com] to download old versions of  Windows plug-ins
* [http://kb2.adobe.com/cps/142/tn_14266.html Adobe's archived Flash versions page]
* [http://ozten.com/random/perfidies/debug.html Austin's perfidies debug page]
* [http://ozten.com/random/perfidies/debug.html Austin's perfidies debug page]
==Positive Test Cases==


==Negative Test Cases==
==Negative Test Cases==

Latest revision as of 18:57, 8 March 2011

Overview

Bug Lists

  • Open bugs
  • fixed bugs -- note that this list includes PFS and Plugin Directory bugs, too, and is mainly for code updates
    • Once we have Firefox.com in production, we should talk about re-organizing the Bugzilla workflow to be clearer which bugs are specifically for Plugin Check

Found a Bug?

  • Help us, please! File in the "websites" component, product: plugins.mozilla.org, and in the whiteboard field, enter "0.6.0" (without the quotes).

Thanks!

QA/Dev Process

  1. Dev fixes a bug/finishes a page by marking as "resolved fixed", adds the "qawanted" keyword
  2. QA checks,approves by adding the comment "qa-verified-trunk" and removes qawanted keyword, if not QA re-opens bug and also removes qawanted keyword.
  3. If the bug is ready to be pushed to production, anyone can add "push-needed" keyword. If the bug is waiting on a particular launch date, don't add this
  4. Dev pushes to production by leaving comment with revision number, removes "push-needed" keyword from bugs that have them
  5. QA checks on production, marks "verified fixed"

Supported Browsers

  • Internet Explorer 8, 9 (when it comes out from beta)
  • Chrome on Windows, Mac (latest version)
  • Opera on Windows, Mac (latest version)
  • Firefox 3.0, 3.5, 3.6, 4.0
  • Safari 5 on Mac, Windows

Supported Plugins

  • Adobe Flash
  • Adobe Reader Plugin
  • Microsoft Silverlight
  • Divx Web Player
  • Java Embedding Plugin
  • Acrobat Reader
  • MoveNetworks Quantum Media Player (used for videos on ESPN360.com and other major video streaming websites)
  • Quicktime
  • BrowserPlus Plugin

Positive Test Cases

1. Load https://www-trunk.stage.mozilla.com/plugincheck with any of the above supported browsers, using the most recent version of each supported plugin
2. Verify that those plugins have their version # in their "Status", and have a green "Up-to-Date" button, which links to their homepage

1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with an *outdated* version of the plugin (oldversion.com is a great resource for Win32.)
2. Verify that we detect the plugin as out-of-date, list its "Status" as "Outdated Version", and have a yellow "Update" button that links to its homepage

1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with a vulnerable version of the plugin (oldversion.com is a great resource for Win32.)
2. Verify that we detect the plugins as vulnerable, and link the user, via an orange "! Update Now" button, to the plugin vendor's homepage

1. Load https://www-trunk.stage.mozilla.com/plugincheck with the supported browsers, but with an unknown plugin
2. Verify that we detect the plugin as "Unknown Plugin" in its "Status", and link the user, via a Google search (e.g. http://www.google.com/search?q=current%20version%20plugin%20iTunes%20Application%20Detector) for that plugin

Staging Server

Links to Useful Resources

Negative Test Cases

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/PluginCheck&oldid=289691"