QA/Execution/Web Testing/PluginCheck: Difference between revisions
| Line 30: | Line 30: | ||
==Positive Test Cases== | ==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> | 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 | 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> | 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, and | 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> | 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 | 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== | ==Staging Server== | ||
Revision as of 19:57, 15 October 2010
Overview
- Project homepage: https://wiki.mozilla.org/Plugins:PluginCheck/CrossBrowserRelease (slightly outdated, but still useful)
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
- Raymond, please fill me in
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+
- 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
Open Bugs
Fixed Bugs to Verify
Links to Useful Resources
- Oldversion.com to download old versions of Windows plug-ins
- Adobe's archived Flash versions page
- Austin's perfidies debug page