|Deletions are marked like this.||Additions are marked like this.|
|Line 25:||Line 25:|
| * [[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|Global Jam testcases]]
* [[http://qa.ubuntu.com/getting-involved/|Getting Involved in quality]]
|Line 42:||Line 40:|
|Milestones will be setup on all three trackers, a summary of what all can be tested can be found on [[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|this milestone page]].||Milestones should be setup on all three trackers.|
|Line 80:||Line 78:|
|[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|Global Jam Testcases]]||[[http://iso.qa.ubuntu.com/|Image Testcases]]|
|Line 91:||Line 89:|
|[[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Cadence Testing Walkthrough]]||[[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Application Testing Walkthrough]]|
|Line 96:||Line 94:|
|[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|Global Jam Testcases]]||[[http://packages.qa.ubuntu.com/|Application Testcases]]|
|Line 113:||Line 111:|
|[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|Global Jam Testcases]]||[[laptop.qa.ubuntu.com|HardwareTestcases]]|
Preparing for the Session
You are encouraged to familiarize yourself with each type of testing in advance so you have a basic understanding of what to expect. In addition, it's encouraged for you to read the following pages:
For each of the different types of testing a milestone is setup on each tracker with the testcases ready to and and results ready to be reported against. See the tests on this milestone page
Note that unless folks are willing to do installations (via VM or real hardware) they will be testing using the live session of the image they brought with them (by booting it up into a VM or on real hardware).
Asking people to prepare for the Jam
Have participants choose what ways they would like to contribute. In general for contributing test results, they should plan to bring a copy of the latest daily image, or provide an up-to-date installation of the development version of ubuntu.
Get help on #ubuntu-quality on freenode.
Holding the Session
Provide an overview of each type of testing and let folks know they can choose to do any or all of the different types during the jam. See the testing descriptions on the second half of this page; feel free to provide the descriptions and links to folks who attend the session.
Milestones should be setup on all three trackers.
If folks are interested in contributing testcases instead of results, direct them to the resources found on the QATeam wiki. In addition, refer them to the applicable launchpad project as needed.
Testing is split into 2 main parts.
- Contributing Results
- Contributing Tests
The following descriptions can be used to help people decide which area they wish to contribute to.
Most users will likely be interested in contributing test results for ubuntu during the jam. There are 3 different types of results contributions that can be made.
- Image Testing
- Application Testing
- Hardware Testing
Image or iso testing consists of downloading a copy of the latest daily ISO images, burning them to CDs/USB keys (or loading them into VM's) and running through an installation with them.
What's tested?: Iso image ubiquity / debian installer
Tutorials: ISO Testing walkthrough
Testcases to execute: Image Testcases
Application testing is the manual testing of specific things (test cases) in applications.
What's tested?: Specific ubuntu packages
Tutorials: Application Testing Walkthrough
Note, the ubuntu global milestone is incorporated with the normal cadence testing; hence the walkthrough is valid for the event
Testcases to execute: Application Testcases
Hardware Testing is about the manual testing of specific things (test cases) mainly related to laptop hardware. Smoke tests are used to determine hardware compatibility for the system being tested.
What's tested?: Hardware compatibility with ubuntu
- Laptop/Hardware for testing
Tutorials: Laptop Testing Walkthrough
Testcases to execute: HardwareTestcases
For contributing testcase, there are 3 different types that can be contributed.
Autopilot is a testing tool capable of introspecting applications and generating keyboard and mouse events. Autopilot tests are utilized for functional testing, including GUI testing and simulating end user interaction.
Autopkg tests are run at build time automatically by the buildbots for the package. The goal of these tests is to provide system and integration testing to guarantee basic functionality.
Manual Testcases are simply sets of instructions designed to be followed and reported against by real people.