Testing

Differences between revisions 28 and 38 (spanning 10 versions)
Revision 28 as of 2013-09-09 13:59:46
Size: 6464
Editor: nskaggs
Comment:
Revision 38 as of 2015-07-28 21:25:13
Size: 4803
Editor: nskaggs
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
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: '''If you are interested in testing, also consider testing snappy. Checkout the [[Jams/Snappy|snappy jam page]] for more information.'''
Line 7: Line 7:
https://wiki.ubuntu.com/Testing/QATracker == Session Host ==
You are encouraged to familiarize yourself with performing the testing in advance so you have a basic understanding of what to expect. This is best done by performing a test yourself before the day of the jam.
Line 9: Line 10:
https://wiki.ubuntu.com/Testing/Activities It is recommended you perform testing on the development version of ubuntu during the jam. To do this, you will be booting a live session of the development version of ubuntu and testing applications. Additionally you may perform an installation of the development version on real hardware or in a virtual machine.
Line 11: Line 12:
https://wiki.ubuntu.com/QATeam/ContributingTestcases == Participants ==
Have participants come prepared with a laptop and usb key (2 gb or greater) that can be wiped clean.
Line 13: Line 15:
 * Ensure they have a [[https://help.launchpad.net/YourAccount/NewAccount|Launchpad/Ubuntu SSO account]]
 * Bring a laptop
 * Bring a usb key (2 gb or greater)
 * Ask them to download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest image]]
 * ''Optionally, if they have a ubuntu phone device, bring it!''
Line 14: Line 21:
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 [[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|this milestone page]] You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them.
Line 16: Line 23:
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). = Holding the Session =
== Setup ==
Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu.
Line 18: Line 27:
= 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.
 * Ensure they have a [[https://help.launchpad.net/YourAccount/NewAccount|Launchpad/Ubuntu SSO account]]
 * Download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest image]]
[[https://wiki.ubuntu.com/QATeam/DevelopmentSetup|Follow the guide]] to ensure each participant has valid a bootable usb stick. Should this cause issues, follow the guide for virtualbox and have them test in a virtual machine.
Line 23: Line 29:
If possible participants should try to test both the installation and the desktop / applications. If participants are unwilling or unable to test the installation, they can focus on testing the desktop instead inside a live session.
Line 24: Line 31:
==== Important links ====
 * [[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|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]]
If / when you find an issue, please be sure and [[https://help.ubuntu.com/community/ReportingBugs|file a bug for it]]!
Line 32: Line 33:
==== Getting Help ====
Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]] on freenode.
== Testing ==
Boot the image and be sure to select the option allowing you to try ubuntu/xubuntu/kubuntu/lubuntu, etc. This will boot into a live session of the default desktop.
Line 35: Line 36:
Once booted into a live session, you are ready to test. Start by performing the application testing below. Once you've completed testing the application testing, it's time to try an install. See the image testing below for this final step.
Line 36: Line 38:
== Holding the Session == Optionally, participants can chose to try out unity8 and test it on there machine.
Line 38: Line 40:
=== Application Testing ===
Testcases to execute:
[[http://packages.qa.ubuntu.com/|Application Testcases]]
Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').
Line 39: Line 45:
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. [[https://wiki.ubuntu.com/Jams/Testing#Testing_Descriptions|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. What is it?: Application testing is the manual testing of specific things (test cases) in applications.
Line 41: Line 47:
What's tested?: The default desktop applications
Line 42: Line 49:
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]].

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
Tutorials:
[[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Application Testing Walkthrough]]
Line 68: Line 53:
Testcases to execute:
[[http://iso.qa.ubuntu.com/|Image Testcases]]
Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').
Line 69: Line 57:
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 is it?: Image or iso testing consists of running through an installation of ubuntu.
Line 75: Line 63:
Line 79: Line 66:
Testcases to execute:
[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|Global Jam Testcases]]
=== Unity8 Testing ===
If you're adventurous and want to check out what the future of Ubuntu is going to hold, see [[Unity8Desktop]] for more information and help with testing Unity8.
Line 82: Line 69:
To file bugs, use the [[https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session|unity8-desktop-session]] package. The unity8 team will reassign your bug if necessary, please file bugs for any issues you find!
Line 83: Line 71:
=== Application Testing === === Phone Testing ===
Got a phone? Try living on the edge for a little while by trying out the development release for the weekend. Flash the [[https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/|devel-proposed channel]] and see what breaks! Although reflashing your phone won't cause you to lose data, make sure you have everything backed up before attempting this.
Line 85: Line 74:
Application testing is the manual testing of specific things (test cases) in applications. == Important links ==
 * [[QATeam/DevelopmentSetup | Testing Setup]]
 * [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]]
 * [[http://packages.qa.ubuntu.com/ | The Package Tracker.]]
Line 87: Line 79:
What's tested?:
Specific ubuntu packages

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/Saucy/Week7|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:

 * Laptop/Hardware for testing

Tutorials:
[[https://wiki.ubuntu.com/Testing/Laptop/Procedures|Laptop Testing Walkthrough]]

Testcases to execute:
[[https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week7|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]]
== Getting Help ==
Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]] on freenode.

Preparing for the Session

If you are interested in testing, also consider testing snappy. Checkout the snappy jam page for more information.

Session Host

You are encouraged to familiarize yourself with performing the testing in advance so you have a basic understanding of what to expect. This is best done by performing a test yourself before the day of the jam.

It is recommended you perform testing on the development version of ubuntu during the jam. To do this, you will be booting a live session of the development version of ubuntu and testing applications. Additionally you may perform an installation of the development version on real hardware or in a virtual machine.

Participants

Have participants come prepared with a laptop and usb key (2 gb or greater) that can be wiped clean.

You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them.

Holding the Session

Setup

Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu.

Follow the guide to ensure each participant has valid a bootable usb stick. Should this cause issues, follow the guide for virtualbox and have them test in a virtual machine.

If possible participants should try to test both the installation and the desktop / applications. If participants are unwilling or unable to test the installation, they can focus on testing the desktop instead inside a live session.

If / when you find an issue, please be sure and file a bug for it!

Testing

Boot the image and be sure to select the option allowing you to try ubuntu/xubuntu/kubuntu/lubuntu, etc. This will boot into a live session of the default desktop.

Once booted into a live session, you are ready to test. Start by performing the application testing below. Once you've completed testing the application testing, it's time to try an install. See the image testing below for this final step.

Optionally, participants can chose to try out unity8 and test it on there machine.

Application Testing

Testcases to execute: Application Testcases Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').

What is it?: Application testing is the manual testing of specific things (test cases) in applications.

What's tested?: The default desktop applications

Tutorials: Application Testing Walkthrough

Image Testing

Testcases to execute: Image Testcases Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').

What is it?: Image or iso testing consists of running through an installation of ubuntu.

What's tested?: Iso image ubiquity / debian installer

Tutorials: ISO Testing walkthrough

Unity8 Testing

If you're adventurous and want to check out what the future of Ubuntu is going to hold, see Unity8Desktop for more information and help with testing Unity8.

To file bugs, use the unity8-desktop-session package. The unity8 team will reassign your bug if necessary, please file bugs for any issues you find!

Phone Testing

Got a phone? Try living on the edge for a little while by trying out the development release for the weekend. Flash the devel-proposed channel and see what breaks! Although reflashing your phone won't cause you to lose data, make sure you have everything backed up before attempting this.

Getting Help

Get help on #ubuntu-quality on freenode.


CategoryJam

Jams/Testing (last edited 2015-07-28 21:25:13 by nskaggs)