Testing

Differences between revisions 34 and 38 (spanning 4 versions)
Revision 34 as of 2015-01-22 22:04:30
Size: 3727
Editor: 184-238-135-103
Comment:
Revision 38 as of 2015-07-28 21:25:13
Size: 4803
Editor: 1
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
'''If you are interested in testing, also consider testing snappy. Checkout the [[Jams/Snappy|snappy jam page]] for more information.'''

== Session Host ==
Line 9: Line 12:
= Asking people to prepare for the Jam = == Participants ==
Line 13: Line 16:
 * Bring a laptop
 * Bring a usb key (2 gb or greater)
Line 14: Line 19:
 * ''Optionally, if they have a ubuntu phone device, bring it!''
Line 15: Line 21:
== Holding the Session ==
Let folks know they will be helping test there hardware and look for bugs in the development version of ubuntu.
You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them.
Line 18: Line 23:
= Holding the Session =
Line 19: Line 25:
Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu.
Line 21: Line 29:
== Contributing Results ==
Line 24: Line 31:
== Booting the image == If / when you find an issue, please be sure and [[https://help.ubuntu.com/community/ReportingBugs|file a bug for it]]!

== Testing ==
Line 27: Line 36:
Once booted into a live session, you can perform application testing. 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.
Line 30: Line 41:
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 31: Line 45:
Application testing is the manual testing of specific things (test cases) in applications. What is it?: Application testing is the manual testing of specific things (test cases) in applications.
Line 33: Line 47:
What's tested?:
Specific packages
Testsuites should exist for each flavor
What's tested?: The default desktop applications
Line 40: Line 52:
=== Image Testing ===
Line 41: Line 54:
[[http://packages.qa.ubuntu.com/|Application Testcases]] [[http://iso.qa.ubuntu.com/|Image Testcases]]
Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').
Line 43: Line 57:
== Getting more advanced ==
Once you've completed testing the defaul
t desktop applications, it's time to try an install.

=== Image Testing ===

Image or iso testing consists of running through an installation of ubuntu.
What is it?: Image or iso testing consists of running through an installation of ubuntu.
Line 57: Line 66:
Testcases to execute:
[[http://iso.qa.ubuntu.com/|Image Testcases]]

== Other forms of testing ==
=== Unity8 Testing ===
Line 63: Line 69:
If you want to file bugs, best 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 any issues you find! 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 65: Line 71:
A priority list can be seen [[https://bugs.launchpad.net/ubuntu/+bugs?field.tag=unity8-desktop|here]]. === 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 67: Line 74:

==
== Important links ====
== Important links ==
Line 73: Line 79:
==== Getting Help ==== == Getting Help ==

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 1)