TestingProcessesUbuntuPersonal

Differences between revisions 6 and 7
Revision 6 as of 2015-06-11 11:34:04
Size: 2684
Editor: vrruiz
Comment:
Revision 7 as of 2015-06-11 13:20:20
Size: 2796
Editor: davmor2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
=== More Info ===
[[https://wiki.ubuntu.com/LandingTeam/SiloTestingGuidelines|More info can be found here]]

WIP

There are a lot of new terms, tools and procedures we want to use for Testing on Ubuntu Personal. This page is here to document those processes.

Silo Testing

Prechecks

  • All merge proposals must have been reviewed and approved.
  • All automated tests must pass.
  • New features must come with automated tests.
  • New strings must be marked for translation.

Installation

Install phablet-tools package in your desktop machine.

  • Flash the phone with the latest development image.
  • citrain device-upgrade <silo number> <password>

  • Overlay PPA
    • In case of Vivid + Overlay PPA, the silo packages need to be pinned to a higher priority. Otherwise, silo packages won't be installed.
    • Create this file: sudo vi /etc/apt/preferences.d/silo.pref

    • Add these lines (silo number must be 0-padded, e.g. landing-001):

Package: *
Pin: release o=LP-PPA-ci-train-ppa-service-landing-<silo number>
Pin-Priority: 1002
  • Save the file.
  • Update the package list: sudo apt-get update

  • Upgrade the packages: sudo apt-get upgrade

Test Plan Locations

Reporting New Cases

Any relevant silo bug should be added to the Regression Test Suite as draft.

More Info

More info can be found here

Tarball Testing

Prechecks

Installation

Test Plan Locations

Reporting New Cases

Sanity Testing

Prechecks

All silos are landed and all tarballs are landed.

Installation

Test Plan Locations

Reporting New Cases

Sanity is a deliberately selected small subset of tests targeting software interactions with hardware. Any additional tests felt required should be discussed with the entire team via the mailing list or standups.

Regression Testing

Prechecks

Sanity Must of been run to ensure the image is at least testable

Installation

Test Plan Locations

Reporting New Cases

New Cases should not be found while testing regression, however you may want make a note here(add a link later) to remind you to look at something during exploratory testing.

Exploratory Testing

Prechecks

Installation

Recording Test and Session

Reporting New Cases

If there is automation required here it should be reported as a bug for the development team.
If there are new manual cases they should be put into draft for review in practitest.

Automated Testing

Prechecks

Installation

Test Plan Locations

Reporting Of Failures

QATeam/TestingProcessesUbuntuPersonal (last edited 2015-12-03 13:56:01 by davmor2)