Testing

Differences between revisions 1 and 2
Revision 1 as of 2009-09-11 14:54:23
Size: 390
Editor: c-76-112-233-201
Comment:
Revision 2 as of 2009-09-11 18:56:23
Size: 4144
Editor: 94-171-216-200
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
Testing is split into 2 main parts.

 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.

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.

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.
Line 7: Line 16:

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.
Line 10: Line 29:
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.
Line 11: Line 34:

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.
Line 14: Line 44:

=== Install Testing ===

'''TEST TRACKER'''

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.

'''On The Tracker'''

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

=== Application/System Testing ===

'''The easy bit'''

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.

'''The longer bit'''

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.

Introduction

Testing is split into 2 main parts.

  1. The testing of the installer. This covers Ubiquity (the live cd installer), Debian-installer (the alternate installer) and wubi.
  2. The testing of applications. This is done by everyone who installs the latest developer version of *buntu.

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.

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.

Requirements

A computer.
A Launchpad Account.
A current CD or ISO.
A network connection.
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.
Check All the above to ensure you can use vm.
Install your chosen vm, unless running on hardware.

Material

Important links:
The Iso Tracker.
Using VirtualBox (older version but works pretty much the same now).
Towards the bottom half of the page gives you the general idea for a kvm command.
Links to the testcases.
The Example-content package if not running on Ubuntu.

Holding the Session

Introduction Session

Install Testing

TEST TRACKER

First things first lets split the team between hardware installed/installing and vm users.
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.
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.

On The Tracker

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.
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.
This helps the developers and release team fix issue for the next release.
Once the install is complete please move on to the Application/System testing.

Application/System Testing

The easy bit

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.

The longer bit

Okay so the system testing is out of the way now it's time to start on the main application testing.
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.
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.

Workflow

Tools & Helpful Information

Get help on #ubuntu-testing.


CategoryJam

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