TestingProcessesUbuntuPersonal
3844
Comment:
|
5091
|
Deletions are marked like this. | Additions are marked like this. |
Line 51: | Line 51: |
See Sanity Testing Below for device tarballs | See Sanity Testing Below for device tarballs <<BR>> |
Line 55: | Line 55: |
=== More Info === https://wiki.ubuntu.com/QATeam/ChannelsToFlash |
|
Line 65: | Line 67: |
=== More Info === https://wiki.ubuntu.com/QATeam/ChannelsToFlash |
|
Line 75: | Line 79: |
=== More Info === https://wiki.ubuntu.com/QATeam/ChannelsToFlash |
|
Line 76: | Line 82: |
/!\ Should be carried out by canonical staff only | |
Line 77: | Line 84: |
The area you wish to test is actually functioning. | |
Line 78: | Line 86: |
* Follow the instructions [[https://wiki.ubuntu.com/QATeam/ChannelsToFlash#Image_Testing_Channels|here]] to get the latest image install * Work on the area you have selected |
|
Line 79: | Line 89: |
Use the web form [[https://docs.google.com/a/canonical.com/forms/d/1rqF4V8VMleQQliEaEqzrUke4aiblSbsczK5BWL33DTU/viewform?edit_requested=true#|here]] to keep track of what you test | |
Line 87: | Line 98: |
=== 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 * Knowing what is right * Knowing images are working * Knowing if something is missing 1. What info do you need in bug reports? * https://wiki.ubuntu.com/QATeam/BugReportInclusions lists the basics and the start for wifi and phone logs more to come. * Most packages are listed in the https://wiki.ubuntu.com/Avengers Please look for a bug similar to yours before reporting a new one. |
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.
Contents
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
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
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
- How can the community help?
- The community are the main users of the currently supported devices so:
- Knowing what is wrong
- Knowing what is right
- Knowing images are working
- Knowing if something is missing
- The community are the main users of the currently supported devices so:
- What info do you need in bug reports?
https://wiki.ubuntu.com/QATeam/BugReportInclusions lists the basics and the start for wifi and phone logs more to come.
Most packages are listed in the https://wiki.ubuntu.com/Avengers Please look for a bug similar to yours before reporting a new one.
QATeam/TestingProcessesUbuntuPersonal (last edited 2015-12-03 13:56:01 by 1)