PPA_Testing
|
Size: 2875
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: |
| 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. | ## page was copied from QATeam/PerformingSRUVerification <<Include(QATeam/Header)>> |
| Line 3: | Line 4: |
| == How to find bugs needing verification == | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 5: | Line 6: |
| 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. | = PPA Testing = ||<tablestyle="font-size: 0.9em; margin: 0.5em;" style="padding:0.5em;">{{attachment:IconsPage/flask192x192.png}}|| |
| Line 7: | Line 9: |
| == Identifying how to test == | |
| Line 9: | Line 10: |
| 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. | |
| Line 11: | Line 11: |
| 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. | 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: |
| == How to perform the test == | ''' please install application from ppa:xyz and test'''. [[http://en.wikipedia.org/wiki/Personal_Package_Archive|(What is a ppa?)]] |
| Line 15: | Line 17: |
| After booting into the affected release of Ubuntu the following steps should be taken: | [[https://help.ubuntu.com/community/Applications|(What is an application?)]] |
| Line 17: | Line 19: |
| 1. Install all available updates 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 * what the line looks like for Gutsy 1. Execute 'sudo apt-get update' 1. Install the updated package via 'sudo apt-get install package' or 'sudo apt-get install package=version-number' 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 |
[[https://en.wikipedia.org/wiki/Software_developer|(What is a developer aka dev?)]] |
| Line 27: | Line 21: |
| == Ways to test using virtual machines == | 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 29: | Line 23: |
| In the event that your current release of Ubuntu is not the same as the release of Ubuntu affected by the bug there are many ways for you to still 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 VMWare, virtual box, kvm or qemu. Depending on the nature of the bug report it may also be possible to use a chroot to perform the verification. | 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. 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'''. == How to Install a ppa (aka Adding) == Open a [[https://help.ubuntu.com/community/UsingTheTerminal| 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: 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)