indicator-datetime

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2014-09-09 17:00:21 →
Size: 1031
Editor: 5751f17e
Comment:
← Revision 7 as of 2014-09-17 13:55:23 → ⇥
Size: 3634
Editor: cpe-76-187-224-40
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
bzr cat lp:~ted/indicator-datetime/merge-policy/tests/manual bzr cat lp:indicator-datetime/tests/manual
Line 29: Line 29:
   * 'Upcoming events' is at the top of the menu    * Upcoming is at the top of the menu
Line 31: Line 31:


== Test Case: indicator-datetime/timestamp-wakeup ==
=== Procedure ===
 * Unplug the phone from any USB connection and put it to sleep
        <dd>Reawaken the device.</dt>
   * The indicator should be showing the correct time.


== Test Case: indicator-datetime/new-alarm-wakeup ==
=== Procedure ===
 * Create and save an upcoming alarm in ubuntu-clock-app
 * Unplug the phone from any USB connection and put it to sleep
  <dd>Confirm that the alarm sounds on time even if the phone is asleep.
  (Note: if in doubt about sleep you can see in the syslog whether the
  device actually suspended or whether the suspend was aborted)</dd>
  <dd>Confirm that the screen comes on when the alarm is triggered.<dd>
   * If the device supports haptic feedback, confirm the alarm vibrates.


== Test Case: indicator-datetime/snooze ==
=== Procedure ===
 * Create and save an upcoming alarm in ubuntu-clock-app
 * When the alarm goes off, press the 'Snooze' button
  <dd>The alarm should go away, then reappear N minutes later.
  By default the N is 5 minutes but will be configurable from ubuntu-clock-app.</dd>
 * When the snoozed alarm reappears, press the 'OK' button
   * This time when the alarm is dismissed, it should not reappear.


== Test Case: indicator-datetime/edited-alarm-wakeup ==
=== Procedure ===
 * Edit an alarm that's already passed. (see previous test)
 * Unplug the phone from any USB connection and put it to sleep
  <dd>Confirm that the alarm sounds on time even if the phone is asleep.
  (Note: if in doubt about sleep you can see in the syslog whether the
  device actually suspended or whether the suspend was aborted)</dd>
  <dd>Confirm that the screen comes on when the alarm is triggered.<dd>
   * If the device supports haptic feedback, confirm the alarm vibrates.


== Test Case: indicator-datetime/tell-snap-decision-to-dismiss ==
=== Procedure ===
 <dt>Set an alarm and wait for it to arrive.</td>
   * Alarm should go off at the specified time
 * Press the 'Dismiss' button in the alarm's snap decision popup before the sound stops.
   * Popup should disappear
   * Sound should stop at the same time, rather than playing til the end of the file.



<strong>
    If all actions produce the expected results listed, please [[results#add_result|submit]] a 'passed' result.
    If an action fails, or produces an unexpected result, please [[results#add_result|submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit]] your result</strong>.

The source for this document can be gotten from Bazaar: 

bzr cat lp:indicator-datetime/tests/manual

The source is in the standard manual testing format for Ubuntu QA: Testing/TestCaseFormat

Test Case: indicator-datetime/unity7-items-check

Procedure

  • Log in to a Unity 7 user session

  • Go to the panel and click on the DateTime indicator

    • Ensure there are items in the menu

Test Case: indicator-datetime/unity7-greeter-items-check

Procedure

  • Start a system and wait for the greeter or logout of the current user session

  • Go to the panel and click on the DateTime indicator

    • Ensure there are items in the menu

Test Case: indicator-datetime/unity8-items-check

Procedure

  • Login to a user session running Unity 8
  • Pull down the top panel until it sticks open
  • Navigate through the tabs until "Upcoming events" is shown
    • Upcoming is at the top of the menu
    • The menu is populated with items

Test Case: indicator-datetime/timestamp-wakeup

Procedure

  • Unplug the phone from any USB connection and put it to sleep

    • <dd>Reawaken the device.</dt>

    • The indicator should be showing the correct time.

Test Case: indicator-datetime/new-alarm-wakeup

Procedure

  • Create and save an upcoming alarm in ubuntu-clock-app
  • Unplug the phone from any USB connection and put it to sleep

    • <dd>Confirm that the alarm sounds on time even if the phone is asleep. (Note: if in doubt about sleep you can see in the syslog whether the device actually suspended or whether the suspend was aborted)</dd> <dd>Confirm that the screen comes on when the alarm is triggered.<dd>

    • If the device supports haptic feedback, confirm the alarm vibrates.

Test Case: indicator-datetime/snooze

Procedure

  • Create and save an upcoming alarm in ubuntu-clock-app
  • When the alarm goes off, press the 'Snooze' button

    • <dd>The alarm should go away, then reappear N minutes later. By default the N is 5 minutes but will be configurable from ubuntu-clock-app.</dd>

  • When the snoozed alarm reappears, press the 'OK' button
    • This time when the alarm is dismissed, it should not reappear.

Test Case: indicator-datetime/edited-alarm-wakeup

Procedure

  • Edit an alarm that's already passed. (see previous test)
  • Unplug the phone from any USB connection and put it to sleep

    • <dd>Confirm that the alarm sounds on time even if the phone is asleep. (Note: if in doubt about sleep you can see in the syslog whether the device actually suspended or whether the suspend was aborted)</dd> <dd>Confirm that the screen comes on when the alarm is triggered.<dd>

    • If the device supports haptic feedback, confirm the alarm vibrates.

Test Case: indicator-datetime/tell-snap-decision-to-dismiss

Procedure

  • <dt>Set an alarm and wait for it to arrive.</td>

  • Alarm should go off at the specified time
  • Press the 'Dismiss' button in the alarm's snap decision popup before the sound stops.
    • Popup should disappear
    • Sound should stop at the same time, rather than playing til the end of the file.

<strong>

Process/Merges/TestPlan/indicator-datetime (last edited 2016-05-16 18:28:42 by localhost)