platform-api

Differences between revisions 1 and 11 (spanning 10 versions)
⇤ ← Revision 1 as of 2014-03-26 12:27:41 →
Size: 1448
Editor: rrcs-96-11-81-19
Comment:
← Revision 11 as of 2014-08-29 11:00:31 → ⇥
Size: 1841
Editor: ip-178-203-162-30
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
* '''Test plan for component''': media-hub * '''Test plan for component''': platform-api
Line 3: Line 3:
 * '''Trunk URL''': lp:media-hub
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/media-hub		  * '''Trunk URL''': lp:platform-api
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/platform-api
Line 8: Line 8:
 * Dash video lens
 * mediaplayer-app
 * music-app
 * webbrowser-app
 * mediascanner
 * all other apps that play music or video		  * qtubuntu
 * qtubuntu-sensors
 * location-service
 * unity-mir
 * native, non-Qt applications
Line 19: Line 18:
 * Install latest (trusty-proposed) image on phone
 * Install freshly built MPs that are needed for landing
 * Ensure that all AP tests pass on the device.
 * Plug device into computer and copy videos into "Videos" folder (i.e. /home/phablet/Video)
 * Copy music into "Music" folder (i.e. /home/phablet/Music)
 * Ensure videos are displayed in Video lens
 * Launch video from video lens and ensure that mediaplayer-app is launched in fullscreen mode (no indicator panel)
 * Test that video playback occurs smoothly
 * Test that tapping on the video reveals the toolbar and scrubber
 * Test the scrubber can be used to move forward/back in the moview
 * Test the video can be played multiple times		 Setup:

 * Install latest image on phone
 * Build, push and install all MRs related to the landing
  * Make sure test suites for platform-api and related landings run during build
 * Reboot
 * Run all binaries from libubuntu-application-apiX-tests.
  * These should all report at the end.

== Manual Tests ==

Applications:

 * Ensure Unity8 comes up and that input is delivered to the shell
 * Launch gallery-app, confirm that it comes up and input is delivered correctly.
 * Launch a click application, confirm that it comes up and input is delivered correctly.

Sensors:

 * Launch messaging-app, rotate device and make sure the application rotates accordingly.
 * Rotate keyboard in a rotating app, make sure it rotates at the same time and direction as the base app.
 * Place a phone call, cover proximity sensor. Phone screen should go off, uncover and it should go on.

Alarms:

 * adb shell into the device
 * Stop powerd (the one holding a reference to /dev/alarm): {{{sudo stop powerd}}}
 * Invoke /usr/bin/test_hardware_alarms_api and make sure that alarms are successfully waited for.

* Test plan for component: platform-api

Dependents/Clients

  • qtubuntu
  • qtubuntu-sensors
  • location-service
  • unity-mir
  • native, non-Qt applications

Test Plan

This test plan is not supposed to be complete; use it to guide your manual testing so they don't 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 image on phone
  • Build, push and install all MRs related to the landing
    • Make sure test suites for platform-api and related landings run during build
  • Reboot
  • Run all binaries from libubuntu-application-apiX-tests.
    • These should all report at the end.

Manual Tests

Applications:

  • Ensure Unity8 comes up and that input is delivered to the shell
  • Launch gallery-app, confirm that it comes up and input is delivered correctly.
  • Launch a click application, confirm that it comes up and input is delivered correctly.

Sensors:

  • Launch messaging-app, rotate device and make sure the application rotates accordingly.
  • Rotate keyboard in a rotating app, make sure it rotates at the same time and direction as the base app.
  • Place a phone call, cover proximity sensor. Phone screen should go off, uncover and it should go on.

Alarms:

  • adb shell into the device

  • Stop powerd (the one holding a reference to /dev/alarm): sudo stop powerd

  • Invoke /usr/bin/test_hardware_alarms_api and make sure that alarms are successfully waited for.

Process/Merges/TestPlan/platform-api (last edited 2016-08-02 15:49:32 by localhost)