QA/Firefox3.6/TestPlan:Plugin Update Referrals: Difference between revisions

← Older edit

QA/Firefox3.6/TestPlan:Plugin Update Referrals (view source)

Revision as of 00:26, 28 October 2009

2,105 bytes added , 28 October 2009

m

→‎Test Cases

Tchung

Confirmed users

6,361

edits

@@ Line 4: / Line 4: @@
 * '''Team:'''
    Dev: bmcride, mossop
-   QA: tchung, qa2, Community Volunteer
+   QA: tchung
 = Overview =
@@ Line 22: / Line 22: @@
 = Things We Don't Test =
 * Automatic downloading and updating of plugins
-* the [https://www-trunk.stage.mozilla.com/en-US/plugincheck/# plugin check page] will be tested by WebdevQA team
+* the [https://www.mozilla.com/en-US/plugincheck/ plugin check page] will be tested by WebdevQA team
-= Test Cases (Draft) =
+= Plugin candidates for Updates =
+* Apple (Quicktime)
+* Adobe (Flash, Shockwave, Reader)
+* Microsoft (Silverlight)
+* DivX
+* Sun (Java)
+= Test Cases =
+;Notification Bar
 [[File:NotificationBar.png]]
 * Verify if site has multiple plugin notifications, the order of the notifications will be in: Outdated > Missing > Blocked.
-* ''Out of date plugins''
+** Note that only one of these notifications will appear in the weighted order.
-** Verify your version of your plugin != latest plugin offered
+* ''Out of date plugins (setting severity = 0)''
-** Q. Which db is it checking against to see if the versions match or not?
+** Test a site with an outdated plugin (You may also need to configure the blocklist.xml file and set severity = 0; means outdated)
-** Q. PFS updates or the actual page hosting the plugin?
+*** For example, this will set quicktime to out-of-date:
-** Clicking "Update Plugins" button will take you to a page to update the plugin
+    <pluginItem os="WINNT">
-** If out of date, Verify notification bar will pop down on the page you are trying to access the plugin.  Note the icons, color, and font will change depending on your OS.
+      <match name="description" exp="Flash 9.0"/>
-* ''Blocklisted plugins''
+      <versionRange severity="0"/>
+    </pluginItem>
+    >>This will affect all versions of Flash 9.x on Windows<<
+** Verify notification bar drops down if your version of your plugin != latest plugin offered.  Note the icons, color, and font will change depending on your OS.
+** Clicking "Update Plugins..." button will take you to the mozilla.com page to update the plugin.  The page also lists all the outdated plugins the user has installed (this page tested by webdev)
+* ''Blocklisted plugins (setting severity = 1 or 2)''
 ** Blocklist your plugins using test blocklist.xml settings.  (See [https://wiki.mozilla.org/Extension_Blocklisting:Testing#How_to_Test_With_a_Local_Blocklist_File here] for instructions and configurations)
 ** Verify plugin is blocklist notification bar. Note the icons, color, and font will change depending on your OS.
+** When the blocklist service updates from a periodic check and detects an outdated plugin (that hasn't been warned of before), it shows an alert (via the alerts service) informing the users. Clicking on this alert would open a tab to the plugins page on mozilla.com.
 * ''Missing plugins''
 ** Visit a site that requires a plugin you havent installed yet (flash site, java site, just google and you'll find it)
 ** Verify missing plugins notification bar. Note the icons, color, and font will change depending on your OS.
+;Addons Manager > Plugins Tab
+* Open Addons Manager > Plugins Tab
+** Reflect the plugin information there matches with what's shown on about:plugins
+*** If the plugin is disabled, it will not appear on about:plugins
+** If the plugin is outdated,
+*** Text shows: "A newer, safer version is available. <More information link>"
+*** Plugin icon has a exclamation icon over it
+** If the plugin is blocklisted,  (setting severity = 1 or 2)
+*** Text shows: "Disabled for your protection. <more information link>"
+*** Plugin icon has a exclamation icon over it
+** Verify after updating the plugin to the latest version, the outdated notification disappears.
+** Verify a "Find Updates" button is present on plugins tab.  Button will take user to the mozilla.com plugin check page.
 [[File:pluginsTab.png]]
-* Verify the Plugin tab of the Addons manager
-* Verify Plugin updates when available
+* Plugin Check for Updates
-** Doing a firefox update via AUS
+** With an outdated plugin, Do a help > check for update
-** Q. Will clicking "Find updates" on the addons manager trigger this window?
+** If update is available,
-** Q. where will the upgrade link point to?
+*** User is prompted to update firefox
+*** Verify the update link in the screenshot goes to the mozilla.com plugin check page
+** If no update available, verify check for outdated plugins screen
+** On startup (not after an update), if outdated plugins are detected, open a tab to the outdated plugins page. This would only happen once for a plugin version.
 [[File:PluginsUpdate.png]]
 = Reference =
+* The Tracking Bug: {{bug|514327}}
 * [https://wiki.mozilla.org/Firefox/Projects/Plugin_Update_Referrals Sprint Spec]
 * See [https://wiki.mozilla.org/Plugins:PluginCheck Plugins:PluginCheck] for updates on the website and service side of this problem.
 * See [https://wiki.mozilla.org/Security:ThePluginProblem Security:ThePluginProblem] for some thoughts from Chris Hofmann on the topic.
+* Plugin Check Page
+** Staging [https://www-trunk.stage.mozilla.com/en-US/plugincheck/#  website]
+** Plugin Check [https://wiki.mozilla.org/Website/Sprints/PluginProblem spec]
+** [https://wiki.mozilla.org/Website/Sprints/PluginProblem/Test_Plan WebdevQA TestPlan]