Procedures

Differences between revisions 17 and 18
Revision 17 as of 2008-03-12 13:53:07
Size: 5210
Editor: 85-211-105-62
Comment:
Revision 18 as of 2008-04-17 10:26:44
Size: 5211
Editor: pra14-b18
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * If you do ot already have one, set up a [https://launchpad.net Launchpad] account so you can report bugs. If you have signed up to edit the Ubuntu wiki you will already have a Launchpad account.  * If you do not already have one, set up a [https://launchpad.net Launchpad] account so you can report bugs. If you have signed up to edit the Ubuntu wiki you will already have a Launchpad account.

Include(Testing/Header)

Preparations

What you need

  • A spare computer or hard drive for test installs. (A virtual machine can be used but we would prefer to see more tests performed on a variety of physical hardware.)
  • A moderate level of Linux experience so you are able to find the relevant log files and produce useful bug reports: ReportingBugs

  • Some available time before a milestone release to perform tests and file reports.

Setting up

attachment:isotesting-logo.png

  • If you do not already have one, set up a [https://launchpad.net Launchpad] account so you can report bugs. If you have signed up to edit the Ubuntu wiki you will already have a Launchpad account.

  • Register with the test tracker at [http://iso.qa.ubuntu.com/ iso.qa.ubuntu.com] which lets you report your test results. If you have registered for Brainstorm you already have an account.

  • Select the ISO images you expect to test and look over the relevant test cases, making sure you have the test setup you need.
  • You can sign up for individual test cases on any ISO. This help everyone see which tests are being covered and sends you a notification email when a new build is available, provided you have opted in to email notification (user settings).

attachment:iso-email.png

Downloading images

Daily ISO images are found at [http://cdimage.ubuntu.com cdimage.ubuntu.com]. We advise that you download the images you expect to test ahead of time and use rsync to update them, as this will reduce the turn around time on testing. Rsync only downloads the parts of the image that have changed and typically takes about 10% of the full download time with reasonably fresh images. See [https://help.ubuntu.com/community/RsyncCdImage instructions on using rsync].

attachment:iso-images.png attachment:iso-download.png

The images currently being tested are listed on [http://iso.qa.ubuntu.com/ iso.qa.ubuntu.com] with a direct download link and the appropriate rsync command for your convenience (click attachment:info.png for the download page). Updates to these builds will be announced on #ubuntu-devel, #ubuntu-testing and (optionally) by email.

Testing

In doing specific testing of the CD/DVD images it is important to focus on those aspects that are typically not used by those who simply run the latest unstable version on their system through daily updates (Such testing is of course also extremely valuable). Key points in image testing include image integrity (md5sums), Live CD and installer functionality.

attachment:iso-report.png

Each ISO image has a set of test cases associated with it. Click attachment:test.png on the tracker to see details of the test case and see ["Testing/InstallMethods"] for details on each install method.

To subscribe to a specific ISO and tests, select the flavour from applet menu then the architecture (32 bit, 64 bit) from the list. Then select the tests you wish to subscribe to and then hit subscribe. You will receive an email announcing there are tests available, provided you also opt-in to email notification on your profile.

Reporting results

The test results are tracked on the iso testing tracker website at [http://iso.qa.ubuntu.com/ iso.qa.ubuntu.com]. Once you are registered, you can log in to report your test results. The website is divided into several sections, and results are reported based on the following criteria:

  • Flavor of Ubuntu (e.g., Ubuntu, Kubuntu, Xubuntu, Edubuntu, etc.)
  • Type of CD image (e.g., live or alternate install cd)
  • Method of installation (e.g., manual partitioning, partition resizing, etc.)

Links to the different flavors of Ubuntu are present in left-hand menu.

attachment:iso-menu.png

Adding test reports

When you have conducted a test you can report the results in the ISO tracker with a general comment and bug numbers if applicable.

attachment:testreport.png

When reporting a broken image it is important that you check the that md5sum corresponds to the ISO being tested to confirm that you do indeed have the correct ISO and that it is not corrupted. To check the md5sum of your image, open a terminal and execute:

md5sum imagename.iso

Where "imagename.iso" is the name of the iso image that you have downloaded and want to verify. The reference value can be found in a file named MD5SUMS in the ISO image download directory. If the md5sum is correct you may also want to run the CD self test on the install media you used.

Filing bugs

As with all testing it is important to [https://help.ubuntu.com/community/ReportingBugs file bugs]. If you find a bug, please, search if it has already been reported, and if it hasn't, report it yourself. You should also refer to the [https://wiki.ubuntu.com/DebuggingProcedures bug filing/debugging guide] for that specific package (if available) to make sure you are aware of known issues and have attached the relevant log files.

Testing/ISO/Procedures (last edited 2013-06-04 22:06:26 by CPE-58-168-89-180)