PPA_Testing
|
Size: 4873
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: |
| ||<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. |
## page was copied from QATeam/PerformingSRUVerification <<Include(QATeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = PPA Testing = ||<tablestyle="font-size: 0.9em; margin: 0.5em;" style="padding:0.5em;">{{attachment:IconsPage/flask192x192.png}}|| |
| Line 5: | Line 10: |
| == How to find bugs needing verification == | |
| Line 7: | Line 11: |
| 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]. | During the test cycle, the developers might ask you to perform specific tasks. Such requests might be phrased something like this: |
| Line 9: | Line 13: |
| 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. | ''' please install application from ppa:xyz and test'''. [[http://en.wikipedia.org/wiki/Personal_Package_Archive|(What is a ppa?)]] |
| Line 11: | Line 17: |
| == Identifying how to test == | [[https://help.ubuntu.com/community/Applications|(What is an application?)]] |
| Line 13: | Line 19: |
| 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. | [[https://en.wikipedia.org/wiki/Software_developer|(What is a developer aka dev?)]] |
| Line 15: | Line 21: |
| 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 || |
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 19: | Line 23: |
| 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 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 21: | Line 25: |
| 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 23: | Line 26: |
| == How to perform the test == | 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 25: | Line 28: |
| After booting into the affected release of Ubuntu the following steps should be taken: | == How to Install a ppa (aka Adding) == |
| Line 27: | Line 30: |
| 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 |
Open a [[https://help.ubuntu.com/community/UsingTheTerminal| terminal]] session, then press ENTER after each line separately, as follows: |
| Line 39: | Line 32: |
| == Updating the bug report == | {{{ sudo apt-add-repository ppa:xyz sudo apt-get update sudo apt-get install application }}} |
| Line 41: | Line 38: |
| [[Include(StableReleaseUpdates,,from="== Verification ==", to="[[Anchor")]] | 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 43: | Line 44: |
| == Ways to test using virtual machines == | What the above does: |
| Line 45: | 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. | 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'''''. == How to Remove a ppa == 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. Open a [[https://help.ubuntu.com/community/UsingTheTerminal| 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: 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.''''' == GPG Keys == 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)