ubuntu-system-image

Differences between revisions 4 and 6 (spanning 2 versions)
⇤ ← Revision 4 as of 2014-03-04 21:44:12 →
Size: 2459
Editor: mail
Comment:
← Revision 6 as of 2014-03-07 16:35:13 → ⇥
Size: 3256
Editor: jibel
Comment:
Deletions are marked like this. Additions are marked like this.
Line 49: Line 49:

== Additional tests candidates for automation ==
The following test cases are being automated. Work items are described in this [[https://blueprints.launchpad.net/ubuntu/+spec/qa-t-system-image-upgrade-testing|blueprint]].

=== Testing the image update path ===
 * Test that updates from image n-1 work
 * Test that updates from image n-2 work

=== Testing the image updater software ===
 * Test that the updater software in image n can do an update to a single newer version in a synthetic channel
 * Test that the updater software in image n can do a multi-step update (applying 5? updates in sequence) in a synthetic channel
 * Test that the updater software in image n correctly applies a full-image update when it’s a smaller download than a series of stacked partial upgrades

Dependents/Clients

Dependents:

  • ubuntu-download-manager

Clients:

  • ubuntu-system-settings

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

Test A

  • Flash device to an older version than the current one, e.g. ubuntu-device-flash --channel trusty --revision 174 --bootstrap

  • Install freshly built MPs that are needed for landing, e.g.
    • Make device writable
    • add-apt-repository the relevant PPA
    • apt-get update
    • apt-get install system-image-cli system-image-common system-image-dbus ubuntu-download-manager ubuntu-system-settings

  • Install any new versions of ubuntu-download-manager and ubuntu-system-settings from the same silo

  • Possibly install any new versions of the Qt networking stack that may also be part of the silo
  • Run the following manual tests (automated tests are run during package build and via DEP 8)
    • Open System Settings panel
    • After one second, open Updates panel
    • Watch for progress
    • If update completes and you are prompted to reboot, then the test succeeded
    • Optionally reboot
    • If the test fails, capture the log files

      • adb pull /var/log/system-image/client.log

      • Optionally capture the u-d-m log files (TBD)
  • Install the update, let the system reboot, and then try again. This time you should be up-to-date.

Test B

  • Set the device to download manually.
  • Flash to an older revision

  • Open System Settings and wait for it to say Updates available

  • Click on About this phone

  • Click on Check for Update and wait for it to say Install 1 update

  • Click on Install 1 update and while the files are downloading, swipe up from the bottom and click Back

  • Click on Check for Update again

  • Wait for the Update System overlay to come up, and then install the update, and reboot

Additional tests candidates for automation

The following test cases are being automated. Work items are described in this blueprint.

Testing the image update path

  • Test that updates from image n-1 work
  • Test that updates from image n-2 work

Testing the image updater software

  • Test that the updater software in image n can do an update to a single newer version in a synthetic channel
  • Test that the updater software in image n can do a multi-step update (applying 5? updates in sequence) in a synthetic channel
  • Test that the updater software in image n correctly applies a full-image update when it’s a smaller download than a series of stacked partial upgrades

Process/Merges/TestPlan/ubuntu-system-image (last edited 2016-03-04 20:58:34 by localhost)