Testing
|
Size: 4131
Comment:
|
Size: 5795
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Testing is split into 3 main parts. | Testing is split into 2 main parts. |
| Line 7: | Line 7: |
| 1. Image Testing. | 1. Contributing Tests 1. 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 |
| Line 11: | Line 16: |
| The following descriptions can be used to help people decide how they want to participate. | For contributing testcase, there are 3 different types that can be contributed. |
| Line 13: | Line 18: |
| == Image Testing == | 1. Autopilot 1. Autopkg 1. Manual |
| Line 15: | Line 22: |
| 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 testing them. This brings to light many issues that might have been missed by other early adopters and developers, especially in the CD builds and installers. | The following descriptions can be used to help people decide which area they wish to contribute to. |
| Line 17: | Line 24: |
| == Application Testing == | == Contributing Results == |
| Line 19: | Line 26: |
| Application testing is the manual testing of specific things (test cases) in applications. Regression tests are specific tests for potential breakages from one release to another (they're also relevant for SRU testing, above). | === Image Testing === |
| Line 21: | Line 28: |
| == 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. |
| Line 23: | Line 30: |
| Hardware Testing is about the manual testing of specific things (test cases) mainly related to laptops hardware. The goal is to get Ubuntu to work great on as many different makes and models of laptops as possible and this can be done knowing which hardware works straight off the install CD and which hardware needs configuring or is poorly supported. | What's tested?: Iso image ubiquity / debian installer |
| Line 25: | Line 34: |
| = Requirements = | Requirements: * Launchpad/Ubuntu SSO account * Copy of the iso/image you wish to test |
| Line 27: | Line 38: |
| A computer.<<BR>> A Launchpad Account.<<BR>> An image of the current daily development version of ubuntu<<BR>> A network connection.<<BR>> Finally a virtual machine, such as KVM/Qemu/Virtualbox, unless installing on hardware. |
Tutorials: [[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|ISO Testing walkthrough]] === 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'' === 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]] == Contributing Testcases == === 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]] === 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]] === 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]] |
| Line 34: | Line 91: |
| 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]] |
|
| Line 35: | Line 94: |
| Download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest iso]]<<BR>> | ==== 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]] |
| Line 37: | Line 102: |
| === Material === Important links:<<BR>> [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]]<<BR>> [[http://packages.qa.ubuntu.com/ | The Package Tracker.]]<<BR>> [[http://laptop.qa.ubuntu.com/ | The Hardware Tracker.]]<<BR>> [[Testing/VirtualBox | Using VirtualBox (older version but works pretty much the same now).]]<<BR>> [[Testing/Automation/KVM | Towards the bottom half of the page gives you the general idea for a kvm command.]]<<BR>> |
==== Getting Help ==== Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]] on freenode. |
| Line 47: | Line 106: |
| You are encouraged to perform 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: | 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 50: | Line 109: |
| Line 52: | Line 110: |
| https://wiki.ubuntu.com/QATeam/ContributingTestcases | |
| Line 60: | Line 119: |
| === Application Testing === NOTE: Ubuntu global jam is a milestone, just like cadence testing. Thus the following tutorial can be followed. [[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|https://wiki.ubuntu.com/Testing/Cadence/Walkthrough]] |
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. |
| Line 64: | Line 121: |
| === Install Testing === Follow the guide here: [[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|https://wiki.ubuntu.com/Testing/ISO/Walkthrough]] === Hardware Testing === Boot your hardware up into a Live session, then follow: [[https://wiki.ubuntu.com/Testing/Laptop/Procedures|https://wiki.ubuntu.com/Testing/Laptop/Procedures]] == Tools & Helpful Information == Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]]. |
[[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.
- Contributing Tests
- 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
For contributing testcase, there are 3 different types that can be contributed.
- Autopilot
- Autopkg
- Manual
The following descriptions can be used to help people decide which area they wish to contribute to.
Contributing Results
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
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
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
Contributing Testcases
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.
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.
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
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).
Introduction 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. 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.
Ubuntu Manual Tests Ubuntu Autopilot Tests
Jams/Testing (last edited 2015-07-28 21:25:13 by 1)