Testing

Differences between revisions 2 and 38 (spanning 36 versions)
Revision 2 as of 2009-09-11 18:56:23
Size: 4144
Editor: 94-171-216-200
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 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 =
'''If you are interested in testing, also consider testing snappy. Checkout the [[Jams/Snappy|snappy jam page]] for more information.'''
Line 6: Line 7:
Testing is split into 2 main parts. == 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 8: Line 10:
 1. The testing of the installer. This covers Ubiquity (the live cd installer), Debian-installer (the alternate installer) and wubi.
 1. The testing of applications. This is done by everyone who installs the latest developer version of *buntu.
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:
Most people test these in a virtual environment although by the time beta comes along a lot of user will now be testing this on real hardware too. == Participants ==
Have participants come prepared with a laptop and usb key (2 gb or greater) that can be wiped clean.
Line 13: Line 15:
I will break down how to test the above in the sections below and describe the usage of the iso test tracker for those that decide to participate.  * 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 15: Line 21:
= Requirements =

A computer.<<BR>>
A Launchpad Account.<<BR>>
A current CD or ISO.<<BR>>
A network connection.<<BR>>
Check if your computer has a cpu with added virtualization:
{{{
egrep '(vmx|svm)' /proc/cpuinfo
}}}
Finally a vm KVM/Qemu/Virtualbox, unless installing on hardware.

== Asking people to prepare for the Jam ==

Grabbing a copy of the latest iso.<<BR>>
Check All the above to ensure you can use vm.<<BR>>
Install your chosen vm, unless running on hardware.

=== Material ===

Important links:<<BR>>
[[http://iso.qa.ubuntu.com/ | The Iso Tracker.]]<<BR>>
[[https://wiki.ubuntu.com/Testing/VirtualBox | Using VirtualBox (older version but works pretty much the same now).]]<<BR>>
[[https://wiki.ubuntu.com/Testing/Automation/KVM | Towards the bottom half of the page gives you the general idea for a kvm command.]]<<BR>>
[[http://testcases.qa.ubuntu.com/ | Links to the testcases.]]<<BR>>
The Example-content package if not running on Ubuntu.
You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them.
Line 43: Line 24:
== Introduction Session == == Setup ==
Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu.
Line 45: Line 27:
=== Install Testing === [[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 47: Line 29:
'''TEST TRACKER''' 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 49: Line 31:
First things first lets split the team between hardware installed/installing and vm users.<<BR>>
Next for those new to the process lets set up a tracker account. Goto http://iso.qa.ubuntu.com click on '''Log In''' then on '''Create New Account''' fill in your details and then click on '''ISO tracker'''.<<BR>>
Now you have access to the tracker you can select the type of install you wish to perform. Start with the iso type you have and then the partitioning type.
If / when you find an issue, please be sure and [[https://help.ubuntu.com/community/ReportingBugs|file a bug for it]]!
Line 53: Line 33:
'''On The Tracker''' == 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 55: Line 36:
Now you have selected your install type you can goto the '''Additional instructions are available for this testcase, click here to read them.''' this will then tell you the steps to run through to install using your selected method.<<BR>>
Once you complete the install please mark if the test passed or failed and any bugs you have found by adding the bug number to the boxes provided.<<BR>>
This helps the developers and release team fix issue for the next release.<<BR>>
Once the install is complete please move on to the '''Application/System 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.
Line 60: Line 38:
=== Application/System Testing === Optionally, participants can chose to try out unity8 and test it on there machine.
Line 62: Line 40:
'''The easy bit''' === 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 64: Line 45:
Goto System->Administration->System Testing. Run through the application filling in the yes no questions at the end you'll be asked for your LaunchPad id and password. This is because the information about you machine is stored in your Launchpad account at '''https://edge.launchpad.net/~yourusername/+hwdb-submissions'''. This is especially useful if you hit hardware regression as you can add you HW id into your bug report. What is it?: Application testing is the manual testing of specific things (test cases) in applications.
Line 66: Line 47:
'''The longer bit''' What's tested?: The default desktop applications
Line 68: Line 49:
Okay so the system testing is out of the way now it's time to start on the main application testing.<<BR>>
First off if your not running Ubuntu install the example-content package. This gives you example files to test applications for media, documents and pictures.<<BR>>
Secondly start running through the applications one at a time till you're happy they are working. For the most part this will involve opening the application, running the application, closing the application. For examples on what to test goto http://testcases.qa.ubuntu.com/Applications/ this currently covers most of the default installed applications.
Tutorials:
[[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Application Testing Walkthrough]]
Line 72: Line 52:
=== Image Testing ===
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 73: Line 57:
== Workflow == What is it?: Image or iso testing consists of running through an installation of ubuntu.
Line 75: Line 59:
== Tools & Helpful Information == What's tested?:
Iso image
ubiquity / debian installer
Line 77: Line 63:
Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-testing|#ubuntu-testing]]. Tutorials:
[[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|ISO Testing walkthrough]]
Line 79: Line 66:
=== 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 80: 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!

=== 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.

== Important links ==
 * [[QATeam/DevelopmentSetup | Testing Setup]]
 * [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]]
 * [[http://packages.qa.ubuntu.com/ | The Package Tracker.]]

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