unity-scope-click

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2014-02-10 12:20:50 →
Size: 58
Editor: p5DDB0E17
Comment:
← Revision 2 as of 2014-02-10 12:39:49 → ⇥
Size: 1690
Editor: host156
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe Process/Merges/TestPlan/unity-scope-click here.  * Test plan for component unity-scope-click

  * Component checklist https://wiki.ubuntu.com/Process/Merges/Checklists/unity-scope-click [not there yet]
  * Trunk URL lp:unity-scope-click
  * Ubuntu Package URL: https://launchpad.net/ubuntu/+source/unity-scope-click

-------------------

= Test Plan =

This test plan is not supposed to be complete; use it to guide your manual testing so they dont miss big functional areas that are part in the component; also this should be used as guideline to inspire the exploratory testing which should be adapted smartly based on the real content of a MP

 * Install latest (trusty-proposed) image on phone

 * Install freshly build MPs that are needed for landing

 * Open dash, go to app scope

  * Check that there is content in both My Apps and Available Apps categories

  * Check that there is no duplication between categories

 * Do a search for an installed app

  * Check result, open app preview

  * Verify it offers option to launch the app, preview looks correct

  * Repeat for one of the apps that's still not a click package

 * Do a search for a not installed app

  * Check result, open app preview

  * Verify it offers option to install

  * Install, verify progress works correctly

  * Verify you can go back and forth in the dash and progress still works (use a larger app, like sleepytime)

 * Once installed a new app, go back to the app scope

  * Verify that the app is listed only in the installed apps list

  * Open preview, verify data, and launch option

  * Launch it, verify it opens correctly. If it doesn't, chack a few more apps to discard specific app issues.

Test Plan

This test plan is not supposed to be complete; use it to guide your manual testing so they dont miss big functional areas that are part in the component; also this should be used as guideline to inspire the exploratory testing which should be adapted smartly based on the real content of a MP

  • Install latest (trusty-proposed) image on phone
  • Install freshly build MPs that are needed for landing
  • Open dash, go to app scope
    • Check that there is content in both My Apps and Available Apps categories
    • Check that there is no duplication between categories
  • Do a search for an installed app
    • Check result, open app preview
    • Verify it offers option to launch the app, preview looks correct
    • Repeat for one of the apps that's still not a click package
  • Do a search for a not installed app
    • Check result, open app preview
    • Verify it offers option to install
    • Install, verify progress works correctly
    • Verify you can go back and forth in the dash and progress still works (use a larger app, like sleepytime)
  • Once installed a new app, go back to the app scope
    • Verify that the app is listed only in the installed apps list
    • Open preview, verify data, and launch option
    • Launch it, verify it opens correctly. If it doesn't, chack a few more apps to discard specific app issues.

Process/Merges/TestPlan/unity-scope-click (last edited 2016-09-22 18:17:33 by localhost)