Testing

Differences between revisions 15 and 16
Revision 15 as of 2013-02-11 17:11:01
Size: 3821
Editor: adsl-98-70-144-146
Comment:
Revision 16 as of 2013-02-11 17:11:25
Size: 3821
Editor: adsl-98-70-144-146
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Testing Descriptions =
Line 10: Line 11:
= Testing Descriptions =

Testing Descriptions

Testing is split into 3 main parts.

  1. Image Testing.
  2. Application Testing
  3. Hardware Testing

The following descriptions can be used to help people decide how they want to participate.

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

Application Testing

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

Hardware Testing

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.

Requirements

A computer.
A Launchpad Account.
An image of the current daily development version of ubuntu
A network connection.
Finally a virtual machine, such as KVM/Qemu/Virtualbox, unless installing on hardware.

Asking people to prepare for the Jam

Download a copy of the latest iso

Material

Important links:
The Iso Tracker.
The Package Tracker.
The Hardware 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.

Holding the Session

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:

https://wiki.ubuntu.com/Testing/QATracker

https://wiki.ubuntu.com/Testing/Activities

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.

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.

Application Testing

NOTE: Ubuntu global jam is a milestone, just like cadence testing. Thus the tutorial can be followed. https://wiki.ubuntu.com/Testing/Cadence/Walkthrough

Install Testing

Follow the guide here: 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

Tools & Helpful Information

Get help on #ubuntu-quality.


CategoryJam

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