platform-api

Differences between revisions 10 and 11
Revision 10 as of 2014-05-19 14:30:58
Size: 1757
Editor: ip-178-203-160-22
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 44: Line 44:
 * Stop powerd (the one holding a reference to /dev/alarm): {{{sudo stop powerd}}}

* 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)