webapp-container

Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2014-01-28 21:06:16
Size: 1307
Editor: pool-173-48-216-79
Comment:
Revision 12 as of 2014-10-01 17:32:00
Size: 3782
Editor: AMontsouris-653-1-240-95
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
* '''Test plan for component''': webbrowser-app
 * '''Component Checklist''': https://wiki.ubuntu.com/Process/Merges/Checklists/system-apps
## page was copied from Process/Merges/TestPlan/webbrowser-app
* '''Test plan for component''': webapp-container
 * '''Component Checklist''':
Line 8: Line 9:
 NONE All webapps, on both desktop and touch, ie:
 * unity-webapps-*
 * and apps maintained in the http://launchpad.net/ubuntu/+source/webapps-core project
Line 14: Line 17:
=== Setup ===
Line 15: Line 20:
 * Install freshly build MPs that are needed for landing  * Use citrain-{slurp,push} to make a clean install of a silo or MP set
Line 17: Line 22:
 * Test browsing different sites by entering a url in the url bar
 * Test navigation by clicking links in a webpage
 * Test navigation by pressing back button
 * Test press and hold on a link and ensure pop-up menu is displayed and functioning
 * Test create and navigating between tabs
 * Test that history is being updated on the activity page
 * Test that navigating to a page from history
 * Test that bookmark/unbookmark a page
 * Test that auto suggestion popup appears correctly when typing in url bar
 

=== General verifications ===

 * Launch the top-10 webapps on the desktop
 * Verify the main features for each of them: login, sending messages, browsing content, watching videos, playing music when relevant
 * Verify that links leading to external content are re-directed to the default browser application
 * Verify that the use is not ejected to the browser during the normal use of a webapp. Those may indicate URL pattern issues
 * If the webapp is displaying a title bar with navigation buttons, verify that the back button is operational
 * Verify that no transparent header appears at the top of the webapp UI (https://launchpad.net/bugs/1305834)
 * Verify that the container displays an error in the absence of network; that the reload button works when the link is back (https://bugs.launchpad.net/webbrowser-app/+bug/1309138)

=== Desktop test cases ===

 * Verify the installation of a webapp on the desktop
  * remove an existing webapp by going into FF or Chrome preferences > Installed websites > uncheck the site(s) you want to test re-installing (ideally all)
  * restart your browser
  * navigate to one of the site managed on our list of top-10 webapps
  * verify that you see a prompt to install the webapp (infobar in the browser)
  * answer yes and verify that a new icon appears on the launcher bar
  * start the webapp with the new launcher
  * verify that the launcher icon is associated with the webapp window; switch back to other app windows and back to the webapp with its launcher icon
  * stop the webapp, and restart it; verify that the icon did not disappear (ie was properly locked on your launcher bar)
 * Verify that no webapp desktop file persists in ~/.local/share/applications

=== Online Accounts Integration ===

 * Start without a Facebook account declared in System Settings
  * Open the Facebook webapp
  * Verify that the application opens an account creation prompt session to create a new account
  * Proceed with the account creation process and accept that Ubuntu be able to use the Facebook permissions summarized at the end of the account creation process
  * Verify that once done (the Trust Session Prompt closes), you are returned to the webapp and automatically logged in

 * Close the app; Re-start the Facebook webapp
 * Verify that you are automatically logged in

 * Quit the Facebook webapp
 * Go to System Settings > Accounts > Facebook > De-authorize the webapp
 * Open the Facebook webapp
 * Verify that the webapp requests your authorization to use the Facebook account

 * Suppress the Facebook account in System Settings
 * Open the Facebook webapp
 * During the account creation process that follows, select to cancel the process
 * Verify that the Facebook webapp exists and returns you to the Dash

* Test plan for component: webapp-container

Dependents/Clients

All webapps, on both desktop and touch, ie:

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

Setup

  • Install latest (trusty-proposed) image on phone
  • Use citrain-{slurp,push} to make a clean install of a silo or MP set
  • Ensure that all AP tests pass on the device.

General verifications

  • Launch the top-10 webapps on the desktop
  • Verify the main features for each of them: login, sending messages, browsing content, watching videos, playing music when relevant
  • Verify that links leading to external content are re-directed to the default browser application
  • Verify that the use is not ejected to the browser during the normal use of a webapp. Those may indicate URL pattern issues
  • If the webapp is displaying a title bar with navigation buttons, verify that the back button is operational
  • Verify that no transparent header appears at the top of the webapp UI (https://launchpad.net/bugs/1305834)

  • Verify that the container displays an error in the absence of network; that the reload button works when the link is back (https://bugs.launchpad.net/webbrowser-app/+bug/1309138)

Desktop test cases

  • Verify the installation of a webapp on the desktop
    • remove an existing webapp by going into FF or Chrome preferences > Installed websites > uncheck the site(s) you want to test re-installing (ideally all)

    • restart your browser
    • navigate to one of the site managed on our list of top-10 webapps
    • verify that you see a prompt to install the webapp (infobar in the browser)
    • answer yes and verify that a new icon appears on the launcher bar
    • start the webapp with the new launcher
    • verify that the launcher icon is associated with the webapp window; switch back to other app windows and back to the webapp with its launcher icon
    • stop the webapp, and restart it; verify that the icon did not disappear (ie was properly locked on your launcher bar)
  • Verify that no webapp desktop file persists in ~/.local/share/applications

Online Accounts Integration

  • Start without a Facebook account declared in System Settings
    • Open the Facebook webapp
    • Verify that the application opens an account creation prompt session to create a new account
    • Proceed with the account creation process and accept that Ubuntu be able to use the Facebook permissions summarized at the end of the account creation process
    • Verify that once done (the Trust Session Prompt closes), you are returned to the webapp and automatically logged in
  • Close the app; Re-start the Facebook webapp
  • Verify that you are automatically logged in
  • Quit the Facebook webapp
  • Go to System Settings > Accounts > Facebook > De-authorize the webapp

  • Open the Facebook webapp
  • Verify that the webapp requests your authorization to use the Facebook account
  • Suppress the Facebook account in System Settings
  • Open the Facebook webapp
  • During the account creation process that follows, select to cancel the process
  • Verify that the Facebook webapp exists and returns you to the Dash

Process/Merges/TestPlan/webapp-container (last edited 2015-11-10 17:11:40 by modemcable092)