indicator-display

Differences between revisions 1 and 13 (spanning 12 versions)
Revision 1 as of 2014-09-05 20:08:30
Size: 58
Editor: cpe-76-187-224-40
Comment:
Revision 13 as of 2016-04-21 17:02:56
Size: 4088
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe Process/Merges/TestPlan/indicator-display here. The source for this document can be gotten from Bazaar:

{{{
bzr cat lp:indicator-display/tests/manual
}}}

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

== Test Case: indicator-display/adb-prompt ==
=== Procedure ===
  * Ensure your computer is not on your device's whitelist for promptless ADB connections. If any computers are whitelisted, they are stored on the device in {{{/data/misc/adb/adb_keys}}} and you can safely remove your computer from it by (A) either removing the file or removing the line that contains your laptop's public key (the line matching {{{~/.android/adbkey.pub}}} on your computer), then (B) reboot the device or {{{sudo restart android-tools-adbd}}}.
  * Turn off your device's screen.
  * Connect your computer to your device with a USB cable.
    * The device screen should come on, showing the lockscreen.
  * Unlock the device.
    * ''After unlocking'', an ADB prompt should appear asking whether or not to allow USB debugging.
    * The ADB prompt should show your computer's fingerprint. This can be checked by running {{{"$ awk '{print $1}' < ~/.android/adbkey.pub | openssl base64 -A -d -a | openssl md5 -c"}}} [[http://android.stackexchange.com/questions/50922/how-can-i-see-the-fingerprint-of-my-adbkey|(Source)]] on your computer.
  * Click "Don't Allow".
    * The prompt should disappear.
  * Try to log into the device from the computer, eg via {{{phablet-shell}}}.
    * The login attempt should fail.
  * Disconnect and reconnect the device's USB cable.
    * The ADB prompt should reappear.
  * Don't touch the ADB prompt. Instead, disconnect the device's USB cable.
    * The ADB prompt should disappear.
  * Reconnect the device's USB cable.
    * The ADB prompt should reappear.
  * Don't touch the ADB prompt. Instead, disconnect the device's USB cable.
  * Turn off the device's screen.
  * Reconnect the device's USB cable.
    * The device screen should come on, showing the lockscreen.
  * Unlock the device.
    * After unlocking, the ADB prompt should reappear.
  * Click "Allow".
  * Try to log into the device from the computer.
    * The login attempt should now succeed. (NB: as always, phablet-shell may take a few tries to connect :) )
  * Disconnect and reconnect the device's USB cable.
    * The device should be remembered, so no prompt should appear.
  * Try to log into the device from the computer.
    * The device should be remembered, so the login attempt should succeed.

== Test Case: indicator-display/adb-prompt-after-boot ==
=== Procedure ===
  * Follow step 1 of indicator-display/adb-prompt test to ensure your computer is not on your device's whitelist for promptless ADB connections.
  * Connect your computer and device with a USB cable
  * Hold down the device's power button and tap "Restart" to reboot the phone
  * Wait for the phone to reboot and the lockscreen to appear
    * The USB Debugging prompt should not appear
  * Unplug the USB cable from the device, then reconnect it
    * The USB Debugging prompt should not appear
  * Unlock the device
    * The USB Debugging prompt should appear

== Test Case: indicator-display/rotation-indicator ==
=== Procedure ===
 * On the phone, enable the rotation lock in ubuntu-system-settings.
   * The rotation lock indicator should appear, and its switch menuitem should be set to 'true'.

        * With the rotation locked, click on the indicator's switch menuitem to toggle from locked to unlocked.
   * The rotation lock indicator should disappear
   * In ubuntu-system-settings, the rotation lock control should change to 'none'.



<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-display/tests/manual

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

Test Case: indicator-display/adb-prompt

Procedure

  • Ensure your computer is not on your device's whitelist for promptless ADB connections. If any computers are whitelisted, they are stored on the device in /data/misc/adb/adb_keys and you can safely remove your computer from it by (A) either removing the file or removing the line that contains your laptop's public key (the line matching ~/.android/adbkey.pub on your computer), then (B) reboot the device or sudo restart android-tools-adbd.

  • Turn off your device's screen.
  • Connect your computer to your device with a USB cable.
    • The device screen should come on, showing the lockscreen.
  • Unlock the device.
    • After unlocking, an ADB prompt should appear asking whether or not to allow USB debugging.

    • The ADB prompt should show your computer's fingerprint. This can be checked by running "$ awk '{print $1}' < ~/.android/adbkey.pub | openssl base64 -A -d -a | openssl md5 -c" (Source) on your computer.

  • Click "Don't Allow".
    • The prompt should disappear.
  • Try to log into the device from the computer, eg via phablet-shell.

    • The login attempt should fail.
  • Disconnect and reconnect the device's USB cable.
    • The ADB prompt should reappear.
  • Don't touch the ADB prompt. Instead, disconnect the device's USB cable.
    • The ADB prompt should disappear.
  • Reconnect the device's USB cable.
    • The ADB prompt should reappear.
  • Don't touch the ADB prompt. Instead, disconnect the device's USB cable.
  • Turn off the device's screen.
  • Reconnect the device's USB cable.
    • The device screen should come on, showing the lockscreen.
  • Unlock the device.
    • After unlocking, the ADB prompt should reappear.
  • Click "Allow".
  • Try to log into the device from the computer.
    • The login attempt should now succeed. (NB: as always, phablet-shell may take a few tries to connect Smile :) )

  • Disconnect and reconnect the device's USB cable.
    • The device should be remembered, so no prompt should appear.
  • Try to log into the device from the computer.
    • The device should be remembered, so the login attempt should succeed.

Test Case: indicator-display/adb-prompt-after-boot

Procedure

  • Follow step 1 of indicator-display/adb-prompt test to ensure your computer is not on your device's whitelist for promptless ADB connections.
  • Connect your computer and device with a USB cable
  • Hold down the device's power button and tap "Restart" to reboot the phone
  • Wait for the phone to reboot and the lockscreen to appear
    • The USB Debugging prompt should not appear
  • Unplug the USB cable from the device, then reconnect it
    • The USB Debugging prompt should not appear
  • Unlock the device
    • The USB Debugging prompt should appear

Test Case: indicator-display/rotation-indicator

Procedure

  • On the phone, enable the rotation lock in ubuntu-system-settings.
    • The rotation lock indicator should appear, and its switch menuitem should be set to 'true'.
      • With the rotation locked, click on the indicator's switch menuitem to toggle from locked to unlocked.
    • The rotation lock indicator should disappear
    • In ubuntu-system-settings, the rotation lock control should change to 'none'.

<strong>

Process/Merges/TestPlan/indicator-display (last edited 2016-04-21 17:02:56 by localhost)