Testing
390
Comment:
|
6747
|
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>>|| |
Line 4: | Line 4: |
= Introduction = | = 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: |
Line 6: | Line 7: |
= Requirements = | https://wiki.ubuntu.com/Testing/QATracker |
Line 8: | Line 9: |
== Asking people to prepare for the Jam == | https://wiki.ubuntu.com/Testing/Activities |
Line 10: | Line 11: |
=== Material === = Holding the Session = == Introduction Session == == Workflow == == Tools & Helpful Information == Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-testing|#ubuntu-testing]]. |
https://wiki.ubuntu.com/QATeam/ContributingTestcases |
Line 22: | Line 14: |
For each of the different types of testing a ubuntu global jam milestone should be setup on each tracker with the testcases ready to and and results ready to be reported against. See the tests on [[https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week7UbuntuGlobalJam|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. * Download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest image]] ==== Important links ==== * [[https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week7UbuntuGlobalJam|Global Jam testcases]] * [[http://qa.ubuntu.com/getting-involved/|Getting Involved in quality]] * [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]] * [[http://packages.qa.ubuntu.com/ | The Package Tracker.]] * [[http://laptop.qa.ubuntu.com/ | The Hardware Tracker.]] * [[Testing/VirtualBox | Using VirtualBox]] ==== Getting Help ==== Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#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 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/Raring/Week7UbuntuGlobalJam|this milestone page]]. If folks are interested in contributing testcases instead of results, direct them to the [[https://wiki.ubuntu.com/QATeam/ContributingTestcases|resources found on the QATeam wiki]]. In addition, refer them to the applicable launchpad project as needed. [[https://launchpad.net/ubuntu-manual-tests|Ubuntu Manual Tests]] [[https://launchpad.net/ubuntu-autopilot-tests/|Ubuntu Autopilot Tests]] = Testing Descriptions = Testing is split into 2 main parts. 1. Contributing Results 1. Contributing Tests The following descriptions can be used to help people decide which area they wish to contribute to. == Contributing Results == 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. 1. Image Testing 1. Application Testing 1. Hardware Testing === Image 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 Requirements: * Launchpad/Ubuntu SSO account * Copy of the iso/image you wish to test Tutorials: [[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|ISO Testing walkthrough]] Testcases to execute: [[https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week7UbuntuGlobalJam|Global Jam Testcases]] === Application Testing === Application testing is the manual testing of specific things (test cases) in applications. What's tested?: Specific ubuntu packages Requirements: * Launchpad/Ubuntu SSO account * Development version of ubuntu (installed or via live session from daily image) Tutorials: [[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Cadence 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: [[https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week7UbuntuGlobalJam|Global Jam Testcases]] === Hardware Testing === 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 Requirements: * Launchpad/Ubuntu SSO account * Development version of ubuntu (installed or via live session from daily image) * Laptop/Hardware for testing Tutorials: [[https://wiki.ubuntu.com/Testing/Laptop/Procedures|Laptop Testing Walkthrough]] Testcases to execute: [[https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week7UbuntuGlobalJam|Global Jam Testcases]] == Contributing Testcases == For contributing testcase, there are 3 different types that can be contributed. 1. Autopilot 1. Autopkg 1. Manual === Autopilot === 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. [[https://wiki.ubuntu.com/QATeam/ContributingTestcases/Autopilot|Autopilot Tutorial]] [[https://bugs.launchpad.net/ubuntu-autopilot-tests/+bugs?field.tag=todo|Testcases to contribute]] [[https://launchpad.net/ubuntu-autopilot-tests/|Ubuntu Autopilot Tests Project]] === Autopkg === 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. [[http://developer.ubuntu.com/packaging/html/auto-pkg-test.html|Autopkg Tutorial]] [[https://wiki.ubuntu.com/QATeam/RequiredTests|Testcases to contribute]] === Manual === Manual Testcases are simply sets of instructions designed to be followed and reported against by real people. [[https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual|Manual Testcase Tutorial]] [[https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?field.tag=todo|Testcases to contribute]] [[https://launchpad.net/ubuntu-manual-tests|Ubuntu Manual Tests Project]] |
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:
https://wiki.ubuntu.com/Testing/QATracker
https://wiki.ubuntu.com/Testing/Activities
https://wiki.ubuntu.com/QATeam/ContributingTestcases
For each of the different types of testing a ubuntu global jam milestone should be 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.
Download a copy of the latest image
Important links
Getting Help
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 will be setup on all three trackers, a summary of what all can be tested can be found on this milestone page.
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 Descriptions
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.
Contributing Results
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 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
Requirements:
- Launchpad/Ubuntu SSO account
- Copy of the iso/image you wish to test
Tutorials: ISO Testing walkthrough
Testcases to execute: Global Jam Testcases
Application Testing
Application testing is the manual testing of specific things (test cases) in applications.
What's tested?: Specific ubuntu packages
Requirements:
- Launchpad/Ubuntu SSO account
- Development version of ubuntu (installed or via live session from daily image)
Tutorials: Cadence 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: Global Jam Testcases
Hardware Testing
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
Requirements:
- Launchpad/Ubuntu SSO account
- Development version of ubuntu (installed or via live session from daily image)
- Laptop/Hardware for testing
Tutorials: Laptop Testing Walkthrough
Testcases to execute: Global Jam Testcases
Contributing Testcases
For contributing testcase, there are 3 different types that can be contributed.
- Autopilot
- Autopkg
- Manual
Autopilot
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.
Ubuntu Autopilot Tests Project
Autopkg
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
Manual Testcases are simply sets of instructions designed to be followed and reported against by real people.
Jams/Testing (last edited 2015-07-28 21:25:13 by 1)