PerformingSRUVerification
Size: 1088
Comment:
|
Size: 2362
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
Bugs needing SRU verification can be found by querying for the bug tag in Launchpad [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed] or by looking at the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs]. 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 '''(hw)''' next to the bug number at the Pending Ubuntu SRUs page. | Bugs needing SRU verification can be found by querying Launchpad for the bug tag [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed] or by viewing the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs]. 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 9: | Line 9: |
The first step in identifying how to test is determing 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. (use a screenshot of bug 160176 to show what bugs targeted to a release look like). Alternatively, at the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] page there are sections for each release of Ubunut that is currently supported. In addition to knowing the release or releases of Ubuntu affected you also need to have a detailed steps to recreate the bug. These can be found in the "TEST CASE" section at the end of the bug's description. |
|
Line 11: | Line 15: |
After booting into the affected release of Ubuntu the following steps should be taken: 1. Install all available updates 1. Recreate the bug using the steps identified in the "TEST CASE" 1. Update your '/etc/apt/sources.list' file to include the -proposed repository * what the line looks like for Gutsy 1. Install the updated package via 'sudo apt-get install package' or 'sudo apt-get install package=version-number' 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 |
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.
How to find bugs needing verification
Bugs needing SRU verification can be found by querying Launchpad for the bug tag [https://launchpad.net/ubuntu/+bugs?field.tag=verification-needed verification-needed] or by viewing the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs]. 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 determing 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. (use a screenshot of bug 160176 to show what bugs targeted to a release look like). Alternatively, at the [http://people.ubuntu.com/~ubuntu-archive/pending-sru.html Pending Ubuntu SRUs] page there are sections for each release of Ubunut that is currently supported.
In addition to knowing the release or releases of Ubuntu affected you also need to have a detailed steps to recreate the bug. These can be found in the "TEST CASE" section at the end of the bug's description.
How to perform the test
After booting into the affected release of Ubuntu the following steps should be taken:
- Install all available updates
- Recreate the bug using the steps identified in the "TEST CASE"
- Update your '/etc/apt/sources.list' file to include the -proposed repository
- what the line looks like for Gutsy
- Install the updated package via 'sudo apt-get install package' or 'sudo apt-get install package=version-number'
- Try to recreate the bug using the steps identified in the "TEST CASE"
- Use the software installed by the package in common ways
Ways to test using virtual machines
QATeam/PerformingSRUVerification (last edited 2017-09-27 12:43:57 by vorlon)