PerformingSRUVerification

Differences between revisions 1 and 28 (spanning 27 versions)
⇤ ← Revision 1 as of 2008-01-22 09:50:01 →
Size: 519
Editor: yttrium
Comment:
← Revision 28 as of 2008-07-29 17:42:01 → ⇥
Size: 4903
Editor: 12
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
SRU Verification is the process of testing packages, updated to fix a bug, that exist in the -proposed repository. These packages need testing to ensure that the package continues to function as designed and that the bug is fixed. [[Include(QATeam/Header)]]

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
SRU Verification is the process of testing packages from the -proposed repository, that have been updated to fix bugs. These packages need testing to ensure that the package continues to function as designed and that the bug is fixed. It is also important to ensure no regression has been introduced by the fix. More information about the process can be found at [https://wiki.ubuntu.com/StableReleaseUpdates Stable Release Update] page. To find out how to enable -proposed look at the [https://wiki.ubuntu.com/Testing/EnableProposed Enable Proposed] page.
Line 4: Line 8:
1. Bugs needing verification are tagged [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed].
There are many ways to find bugs needing SRU verification: by viewing the [http://people.ubuntu.com/~sbeattie/sru_todo.html SRU To Do] or [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] or by querying Launchpad for the bug tag [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed] or by looking at bugs which the SRU verification team is [https://bugs.launchpad.net/~sru-verification/+subscribedbugs subscribed].

The Pending Ubuntu SRUs are generated by parsing the changelogs of the packages in -proposed repository. By clicking on '''changelog bugs''' entry you will be taken to the Launchpad bug report (if it exists). Some bugs resolved by -proposed packages require specific hardware and these can be identified by the '''hw-specific''' tag in Launchpad or by the '''(hw)''' next to the bug number at the Pending Ubuntu SRUs page.
Line 8: Line 15:
The first step in identifying how to test, is determining the release or releases of Ubuntu affected by the particular bug. This can be done by looking at the bug report and determining the release affected by the bug.

In the example below the Postgresql8.1 bug affects the Dapper, Feisty, Gutsy and Hardy releases of Ubuntu and should be verified in each one.
  ||<tablestyle="float:center; font-size: 0.75em; background:#C2B8A1;margin: 0 0 1em 1em;" style="padding:0.5em;">[https://wiki.ubuntu.com/QATeam/PerformingSRUVerification?action=AttachFile&do=get&target=bug.png https://wiki.ubuntu.com/QATeam/PerformingSRUVerification?action=AttachFile&do=get&target=bug-tn.png]||
  || Click to zoom ||

Alternatively, at the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] page there are sections for each release of Ubuntu that is currently supported.

In addition to knowing the release or releases of Ubuntu affected you also need to have detailed steps to recreate the bug. These can be found in the "TEST CASE" section at the end of the bug's description. [https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/172264 Bug 172264] has an example of what the test case will look like.
Line 10: Line 27:
After booting into the affected release of Ubuntu the following steps should be taken:

 1. Ensure that your system is up to date by installing all available updated packages from the -updates and -security repositories
 1. Verify that you do not have the proposed package installed by checking the package version using 'dpkg -l PKGNAME | cat'
 1. Recreate the bug using the steps identified in the "TEST CASE"
 1. Modify your '/etc/apt/sources.list' file to include the -proposed repository
  * deb http://archive.ubuntu.com/ubuntu/ hardy-proposed main restricted universe
 1. Execute 'sudo apt-get update'
 1. Install the proposed package via 'sudo apt-get install PKGNAME' or 'sudo apt-get install PKGNAME=VERSION-NUM'
 1. Verify that you installed the correct package version using 'dpkg -l PKGNAME | cat'
 1. Reboot the system
 1. Try to recreate the bug using the steps identified in the "TEST CASE"
 1. Use the software installed by the package in common ways

== Updating the bug report ==

[[Include(StableReleaseUpdates,,from="== Verification ==", to="[[Anchor")]]
Line 11: Line 46:

In the event that your current release of Ubuntu is not the same as the release of Ubuntu affected by the bug there are still many ways for you to perform the verification of the Stable Release Update without installing the affected release on your hardware. This can be done by using an emulator such as [https://wiki.ubuntu.com/Testing/VirtualBox Virtual Box], [https://wiki.ubuntu.com/KvmVirtManagerEtc kvm], [https://help.ubuntu.com/community/Installation/QemuEmulator qemu] or VMware. Virtual machines images for VMware are available at [http://isv-image.ubuntu.com/vmware/]. Depending on the nature of the bug report it may also be possible to use a [https://wiki.ubuntu.com/DebootstrapChroot chroot] to perform the verification.

Include(QATeam/Header)

SRU Verification is the process of testing packages from the -proposed repository, that have been updated to fix bugs. These packages need testing to ensure that the package continues to function as designed and that the bug is fixed. It is also important to ensure no regression has been introduced by the fix. More information about the process can be found at [https://wiki.ubuntu.com/StableReleaseUpdates Stable Release Update] page. To find out how to enable -proposed look at the [https://wiki.ubuntu.com/Testing/EnableProposed Enable Proposed] page.

How to find bugs needing verification

There are many ways to find bugs needing SRU verification: by viewing the [http://people.ubuntu.com/~sbeattie/sru_todo.html SRU To Do] or [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] or by querying Launchpad for the bug tag [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed] or by looking at bugs which the SRU verification team is [https://bugs.launchpad.net/~sru-verification/+subscribedbugs subscribed].

The Pending Ubuntu SRUs are generated by parsing the changelogs of the packages in -proposed repository. By clicking on changelog bugs entry you will be taken to the Launchpad bug report (if it exists). Some bugs resolved by -proposed packages require specific hardware and these can be identified by the hw-specific tag in Launchpad or by the (hw) next to the bug number at the Pending Ubuntu SRUs page.

Identifying how to test

The first step in identifying how to test, is determining the release or releases of Ubuntu affected by the particular bug. This can be done by looking at the bug report and determining the release affected by the bug.

In the example below the Postgresql8.1 bug affects the Dapper, Feisty, Gutsy and Hardy releases of Ubuntu and should be verified in each one.

Alternatively, at the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] page there are sections for each release of Ubuntu that is currently supported.

In addition to knowing the release or releases of Ubuntu affected you also need to have detailed steps to recreate the bug. These can be found in the "TEST CASE" section at the end of the bug's description. [https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/172264 Bug 172264] has an example of what the test case will look like.

How to perform the test

After booting into the affected release of Ubuntu the following steps should be taken:

  1. Ensure that your system is up to date by installing all available updated packages from the -updates and -security repositories
  2. Verify that you do not have the proposed package installed by checking the package version using 'dpkg -l PKGNAME | cat'
  3. Recreate the bug using the steps identified in the "TEST CASE"
  4. Modify your '/etc/apt/sources.list' file to include the -proposed repository
  5. Execute 'sudo apt-get update'
  6. Install the proposed package via 'sudo apt-get install PKGNAME' or 'sudo apt-get install PKGNAME=VERSION-NUM'
  7. Verify that you installed the correct package version using 'dpkg -l PKGNAME | cat'
  8. Reboot the system
  9. Try to recreate the bug using the steps identified in the "TEST CASE"
  10. Use the software installed by the package in common ways

Updating the bug report

Include(StableReleaseUpdates,,from="== Verification ==", to="[[Anchor")

Ways to test using virtual machines

In the event that your current release of Ubuntu is not the same as the release of Ubuntu affected by the bug there are still many ways for you to perform the verification of the Stable Release Update without installing the affected release on your hardware. This can be done by using an emulator such as [https://wiki.ubuntu.com/Testing/VirtualBox Virtual Box], [https://wiki.ubuntu.com/KvmVirtManagerEtc kvm], [https://help.ubuntu.com/community/Installation/QemuEmulator qemu] or VMware. Virtual machines images for VMware are available at [http://isv-image.ubuntu.com/vmware/]. Depending on the nature of the bug report it may also be possible to use a [https://wiki.ubuntu.com/DebootstrapChroot chroot] to perform the verification.

QATeam/PerformingSRUVerification (last edited 2017-09-27 12:43:57 by vorlon)