PPA_Testing
Differences between revisions 32 and 91 (spanning 59 versions)
|
Size: 6769
Comment:
|
← Revision 91 as of 2013-08-03 04:38:53 ⇥
Size: 3802
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was copied from QATeam/PerformingSRUVerification | |
| Line 4: | Line 5: |
| Stable Release Update (SRU) Verification is the process of testing packages from the -proposed repository, that have been updated to fix bugs in a [[https://wiki.ubuntu.com/Releases|stable release]]. 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. | |
| Line 6: | Line 6: |
| 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. | = PPA Testing = ||<tablestyle="font-size: 0.9em; margin: 0.5em;" style="padding:0.5em;">{{attachment:IconsPage/flask192x192.png}}|| |
| Line 9: | Line 10: |
| == How to find bugs needing verification == | |
| Line 11: | Line 11: |
| There are many ways to find bugs needing SRU verification: | During the test cycle, the developers might ask you to perform specific tasks. Such requests might be phrased something like this: |
| Line 13: | Line 13: |
| * by viewing the [[http://people.ubuntu.com/~ubuntu-archive/pending-sru.html|Pending Ubuntu SRUs]], * by querying Launchpad for a specific release (here lucid) and the bug tag [[https://launchpad.net/ubuntu/lucid/+bugs?field.status%3Alist=FIXCOMMITTED&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]]. |
''' please install application from ppa:xyz and test'''. [[http://en.wikipedia.org/wiki/Personal_Package_Archive|(What is a ppa?)]] |
| Line 17: | Line 17: |
| 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). If no changelog bug is displayed, clicking on the version of the package in the '-proposed' column will take you to the changelog entry for that version of the package in launchpad (the bug number may be displayed in the changelog but not in the report if the bug number doesn't respect a standard format) | [[https://help.ubuntu.com/community/Applications|(What is an application?)]] |
| Line 19: | Line 19: |
| 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. | [[https://en.wikipedia.org/wiki/Software_developer|(What is a developer aka dev?)]] |
| Line 21: | Line 21: |
| == Identifying how to test == | As developers talk in code language, you might understand their requests less than you do [[http://en.wikipedia.org/wiki/Klingon#Language | Klingon]]. Wiki writers translate and explain code language for the rest of us to understand. (Go to the Ubuntu Forums, Launchpad mailing lists, Ubuntu channels on freenode IRC, or Facebook if you need human interaction.) |
| Line 23: | Line 23: |
| 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, you will see an application named '''"application"''' from the [[http://en.wikipedia.org/wiki/Personal_Package_Archive|PPA]] named '''"ppa:xyz"'''. These two pieces of information will be given to you by a Dev or via the Ubuntu-Quality mailing list. |
| Line 25: | Line 25: |
| More than one release may be affected by the bug. In that case, the bug needs to be reproduced and the fix needs to be tested for each affected release. | |
| Line 27: | Line 26: |
| 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 || |
If you ever feel unsure of the precise names of either the application or the ppa, please STOP, and ASK the Devs. Do '''NOT''' install ppa's that you do not fully trust because they can be a source of [[http://en.wikipedia.org/wiki/Malware | malware]]. If in doubt.... '''ASK'''. Some PPA's will ask for acceptance of a GPG key. Again, if in doubt about anything, please, don't be shy, '''JUST ASK'''. |
| Line 31: | Line 28: |
| 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. | == How to Install a ppa (aka Adding) == |
| Line 33: | Line 30: |
| 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. | Open a [[https://help.ubuntu.com/community/UsingTheTerminal| terminal]] session, then press ENTER after each line separately, as follows: |
| Line 35: | Line 32: |
| Test cases should be added to the description of the report in a standardised format: | |
| Line 37: | Line 33: |
| TEST CASE: 1. description of step 1 2. description of the step 2 3. ... VERIFICATION DONE What is the expected result at the end of the test. |
sudo apt-add-repository ppa:xyz sudo apt-get update sudo apt-get install application |
| Line 46: | Line 38: |
| Note that the verification-failed is either the subject of the bug report or a regression. | If being asked to accept a GPG key, the steps will be slightly different. At the step {{{ sudo apt-add-repository ppa:xyz }}} you will asked to accept the GPG key. When this message appears, simply press ENTER to accept - provided you trust the PPA. |
| Line 48: | Line 44: |
| Writing the test case is a mandatory step of the [[StableReleaseUpdates|SRU procedure]]. But sometimes, there is no such test case. If the test case is missing and the reproduction steps are not obvious, you can provide one if you can reproduce the issue described in the bug report or set the status to 'In progress', describe why you cannot reproduce and set the verification tag to 'verification-failed'. | What the above does: |
| Line 50: | Line 46: |
| == How to perform the test == | 1. sudo apt-add-repository ppa:xyz '''''- adds the ppa called xyz to your system index''''', 2. sudo apt-get update '''''- tells your system it is there to be used'''''. 3. sudo apt-get install application '''''- installs the application'''''. |
| Line 52: | Line 50: |
| After booting into the affected release of Ubuntu the following steps should be taken: | == How to Remove a ppa == |
| Line 54: | Line 52: |
| 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 as described in [[Testing/EnableProposed|how to enable -proposed]]. * deb http://archive.ubuntu.com/ubuntu/ lucid-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 |
If the new '''application''' does not work, report a [[https://wiki.ubuntu.com/Lubuntu/ReportingBugs | Bug]]. After you report the bug, you may want or need to get rid of the application and re-install the current version. |
| Line 66: | Line 54: |
| Having a look at the patch may help to know exactly which part of the package is affected by the fix and what needs to be more specifically tested. | Open a [[https://help.ubuntu.com/community/UsingTheTerminal| terminal]] session, then press ENTER after each line separately, as follows: |
| Line 68: | Line 56: |
| == Updating the bug report == | {{{ sudo apt-add-repository -r ppa:xyz sudo apt-get update sudo apt-get remove application sudo apt-get install application }}} |
| Line 70: | Line 63: |
| <<Include(StableReleaseUpdates,,from="== Verification ==", to="If you want to help us")>> | What the above does: |
| Line 72: | Line 65: |
| == Tagging the report == | 1. sudo apt-add-repository -r ppa:xyz '''''- removes the test ppa area''''' 2. sudo apt-get update '''''- tells your system that it is no longer to be used''''' 3. sudo apt-get remove application '''''- removes the new version''''' 4. sudo apt-get install application '''''- now that the test ppa is no longer in use, the install will 'grab' the one from the normal area.''''' |
| Line 74: | Line 70: |
| === SRU specific === | |
| Line 76: | Line 71: |
| <<Include(Bugs/Tags,,from='=== SRU Specific ===',to='=== X ')>> | == GPG Keys == |
| Line 78: | Line 73: |
| === Regression specific === <<Include(Bugs/Tags,,from='=== Regression specific ===',to='=== SRU Specific ===')>> == 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 a [[https://help.ubuntu.com/community/VirtualMachines|Virtual Machine] 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 can not be used to reproduce hardware specific issues. 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. |
A full description of GPG keys and their use can be found at [[https://help.ubuntu.com/community/GnuPrivacyGuardHowto | About GPG Keys]]. |
PPA Testing
|
During the test cycle, the developers might ask you to perform specific tasks. Such requests might be phrased something like this:
please install application from ppa:xyz and test.
(What is a developer aka dev?)
As developers talk in code language, you might understand their requests less than you do Klingon. Wiki writers translate and explain code language for the rest of us to understand. (Go to the Ubuntu Forums, Launchpad mailing lists, Ubuntu channels on freenode IRC, or Facebook if you need human interaction.)
In the example below, you will see an application named "application" from the PPA named "ppa:xyz". These two pieces of information will be given to you by a Dev or via the Ubuntu-Quality mailing list.
If you ever feel unsure of the precise names of either the application or the ppa, please STOP, and ASK the Devs. Do NOT install ppa's that you do not fully trust because they can be a source of malware. If in doubt.... ASK. Some PPA's will ask for acceptance of a GPG key. Again, if in doubt about anything, please, don't be shy, JUST ASK.
How to Install a ppa (aka Adding)
Open a terminal session, then press ENTER after each line separately, as follows:
sudo apt-add-repository ppa:xyz sudo apt-get update sudo apt-get install application
If being asked to accept a GPG key, the steps will be slightly different. At the step
sudo apt-add-repository ppa:xyz
you will asked to accept the GPG key. When this message appears, simply press ENTER to accept - provided you trust the PPA.
What the above does:
sudo apt-add-repository ppa:xyz - adds the ppa called xyz to your system index,
sudo apt-get update - tells your system it is there to be used.
sudo apt-get install application - installs the application.
How to Remove a ppa
If the new application does not work, report a Bug. After you report the bug, you may want or need to get rid of the application and re-install the current version.
Open a terminal session, then press ENTER after each line separately, as follows:
sudo apt-add-repository -r ppa:xyz sudo apt-get update sudo apt-get remove application sudo apt-get install application
What the above does:
sudo apt-add-repository -r ppa:xyz - removes the test ppa area
sudo apt-get update - tells your system that it is no longer to be used
sudo apt-get remove application - removes the new version
sudo apt-get install application - now that the test ppa is no longer in use, the install will 'grab' the one from the normal area.
GPG Keys
A full description of GPG keys and their use can be found at About GPG Keys.
QATeam/PPA_Testing (last edited 2013-08-03 04:38:53 by d154-5-184-90)