TestingProcessesUbuntuPersonal

Differences between revisions 11 and 12
Revision 11 as of 2015-06-29 13:49:23
Size: 5443
Editor: davmor2
Comment:
Revision 12 as of 2015-06-29 13:58:34
Size: 5565
Editor: jibel
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<TableOfContents()>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

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 (instructions here )

  • 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

Images are scheduled here

Installation

For Custom Tarballs Read: https://wiki.ubuntu.com/QATeam/ChannelsToFlash#Testing_Custom_Tarballs
For Device Tarballs Read: https://wiki.ubuntu.com/QATeam/ChannelsToFlash#Testing_Device_Tarballs

Test Plan Locations

See Sanity Testing Below for device tarballs
For Custom Tarballs look at practitest (cases need adding here)

Reporting New Cases

All new cases must be added to the "To Review" Queue in practitest

More Info

https://wiki.ubuntu.com/QATeam/ChannelsToFlash

Sanity Testing

Prechecks

All silos are landed and all tarballs are landed.

Installation

  • Follow the instructions here to get the latest image install

  • Then run the sanity suite

Test Plan Locations

Sanity test are located in practitest currently

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.

More Info

https://wiki.ubuntu.com/QATeam/ChannelsToFlash

Regression Testing

Prechecks

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

Installation

  • Follow the instructions here to get the latest image install

  • Then run the regression suite

Test Plan Locations

Regression tests are located in Practitest Currently

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.

More Info

https://wiki.ubuntu.com/QATeam/ChannelsToFlash

Exploratory Testing

Warning /!\ Should be carried out by canonical staff only

Prechecks

The area you wish to test is actually functioning.

Installation

  • Follow the instructions here to get the latest image install

  • Work on the area you have selected

Recording Test and Session

Use the web form here to keep track of what you test

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

More info

FAQ

  1. How can the community help?
    • The community are the main users of the currently supported devices so:
      • Knowing what is wrong (bug reports, see point 2)
      • Knowing what is right (ubuntu-phone@lists.launchpad.net send a mail here the devs would love to know what you love)

      • Knowing images are working (Bug reports when the don't, see point 2)
      • Knowing if something is missing (Bug reports, please don't be dismayed if they get marked as wishlist lot to do, alternatively talking to the development team/creator of you favourite app about a port to Ubuntu is good too Smile :) )

  2. What info do you need in bug reports?

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