Testing

Differences between revisions 29 and 105 (spanning 76 versions)
Revision 29 as of 2013-09-30 16:12:56
Size: 10698
Editor: 2
Comment:
Revision 105 as of 2016-11-16 18:29:19
Size: 4405
Editor: awjinahn
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Testing Ubuntu GNOME = ||<tablestyle="margin: 0 0 2.5rem 0 !important;">[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/German| German]] || [[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Greek| Ελληνικά]] || [[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Korean| 한국어]] ||
Line 5: Line 5:
||<tablestyle="float:right; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| ||<tablestyle="float: right; width: 40%; margin: 1rem 0 1rem 1rem; background: #FFF;" style="padding: 1rem 1.5rem 1.25rem 1.5rem; line-height: 200%;"><<TableOfContents>>||
= Testing =
<<BR>>
||<style="border:none">||<style="padding-top: 0.6em; border: none;">[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/IamNew | {{attachment:UbuntuGNOME/Artwork/Graphics/warning.png}}]]||<style="width: 80%; border: none;" >[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/IamNew | I am New]]||
Line 7: Line 10:
This section is dedicated to the current development version of Ubuntu GNOME. As with all Alphas and Betas they are not suitable for a production environment, please take the time to read [[http://ubuntuforums.org/showthread.php?t=1594833 | Common Questions for Testing]] ||<style="border:none">||<style="padding-top: 0.6em; border: none;">[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Start | {{attachment:UbuntuGNOME/Artwork/Graphics/testing.png}}]]||<style="width: 80%; border: none;" >[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Start | Start Testing]]||
Line 9: Line 12:
 * Download Ubuntu GNOME Saucy Daily Build, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/ | This Link]]. ||<style="border:none">||<style="padding-top: 0.6em; border: none;">[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Join | {{attachment:UbuntuGNOME/Artwork/Graphics/love.png}}]]||<style="width: 80%; border: none;" >[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Join | Join Ubuntu GNOME QA Team]]||
Line 11: Line 14:
##The daily builds for post alpha1 13.10 are now being built on the cron-job. The first set of alterations that will land in 13.10 are now in. ||<style="border:none">||<style="padding-top: 0.6em; border: none;">[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/QAHelp | {{attachment:UbuntuGNOME/Artwork/Graphics/help.png}}]]||<style="width: 80%; border: none;" >[[https://wiki.ubuntu.com/UbuntuGNOME/Testing/QAHelp | Need Help or Have Any Q?]]||
Line 13: Line 16:
## * Download Ubuntu GNOME Saucy Beta 2, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/releases/saucy/beta-2/ | this link]]. <<BR>>
== Bugs ==
<<BR>>
||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffaaaa; font-size: 0.90em;" :> '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' ||
Line 15: Line 21:
 * Please read the [[https://wiki.ubuntu.com/SaucySalamander/Beta2/UbuntuGNOME | release notes for Beta 2]]. ||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffd5d5; font-size: 0.90em;" :> '''[[https://help.ubuntu.com/community/ReportingBugs | How to Report Bugs]]''' ||
Line 17: Line 23:
##The Dailies are now considered as Release Candidates. ||<tablestyle="width: 40%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #ffaaaa; font-size: 0.90em;" :> '''Note:''' It is not uncommon for developers to request the Bug reporter to file the Bug upstream where relevant, obviously the actual reporter can usually provide more info, testing etc. That said, upstream Bugs should really only be submitted once an Ubuntu Developer has requested it. <<BR>><<BR>>'''[[https://wiki.ubuntu.com/Bugs/Upstream/GNOME | Upstream GNOME Bugs]]''' ||
Line 19: Line 25:
== Before Getting Started ==
Testing and using Development Releases of Ubuntu GNOME (or any other flavor of Ubuntu) isn't meant to be for production machines of daily usage. Testing is to make sure the Stable Release is working as good as possible. Find Bugs, Improve Performance, etc - this is what we do until we finalize the testing process and release a stable version. Whenever you are testing, keep in mind few notes:
<<BR>>
== Testing Activities ==
<<BR>>
 * For more information and details about Testing:
||<tablestyle="width: 90%; margin: 5px 0;" style="border: none; border-radius: 10px; background-color: #b9defa; font-size: 0.90em;" :> '''Please head over [[https://wiki.ubuntu.com/UbuntuGNOME/Testing/Activities | Testing Activities Page]] ''' ||
Line 22: Line 31:
 1. Make sure to [[https://help.ubuntu.com/community/BackupYourSystem | Backup]] your '''important data'''. If you are using Linux, the best and easier way is to make a copy of your '''/home''' folder or partition. If you want to do a full system backup, please see [[https://help.ubuntu.com/community/BackupYourSystem | this link]] and [[http://www.howtogeek.com/108869/how-to-back-up-ubuntu-the-easy-way-with-dj-dup/ | this link too]].
 1. You can use [[http://en.wikipedia.org/wiki/Virtual_machine | Virtual Machines]] - for example [[https://help.ubuntu.com/community/VirtualMachines | See this]]. You can use USB Drives or External HDD. You can use your machine. That is totally up to you but please, refer to #1 :)
 1. Using a Development Release is not suitable for daily production machine.
 1. The more you break your installation, the better. That is why, to play it safe, better to use Virtual Machines, Spare Testing Machines and/or USB Drives, specially with Alpha 1 and Alpha 2. Beta Releases are a bit more stable but still under heavy development.
 1. '''The most important part of testing is to actually install the system and check how the installation process will work'''. This is very important. Also, if you have say Alpha 1 installed, it is less helpful to just upgrade it to Alpha 2 or Beta 1. Please, do a fresh new install - you can either [[https://help.ubuntu.com/community/ZsyncCdImage | zsync]] your ISO or download again.
 1. Finally, always remember: '''Better Safe Than Sorry''' :)

== Getting Involved ==
=== I am NEW to Testing, How Can I help? ===
Congratulation, you are the best and perfect candidate who actually can help us testing a development release. If you are new to all this, please read '''[[https://wiki.ubuntu.com/Testing/ISO/Walkthrough | this page]]'''. If you have any question, join the mailing list and just ask :)

=== Ubuntu GNOME Mailing List ===

'''Please do join our [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome | Mailing List]] - this is VERY important'''.

After you join the mailing list, please send an email to introduce yourself. Don't be shy, we don't bite ;) so, Keep Calm and Join Ubuntu GNOME Mailing List :)

=== Share Your Findings or Ask Qs ===
When you compose New Email, please write '''[Testing]''' in your subject so everyone on the list will understand what your email is all about - that you are a tester and helping out.

It is '''VERY''' important to share your findings with the team. Also, you can ask anything on the mailing list as well. So, it is a must-do step :)

##Maybe we do need to create Ubuntu GNOME QA Sub-Team in case we will have more testers joining in.

## == Announcements ==

## There is a weekly digest of the test version available at ##
## [https://wiki.ubuntu.com/Lubuntu/ReleaseStatus/Raring | Release Status]]. It is updated each Friday. If you ## wish for anything to be included or have questions, please contact [[gilir]] by Thursday at the latest.

## At each milestone release, the notes at
## [[https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview | technical overview]] are updated.

##https://wiki.ubuntu.com/UbuntuGNOME/Testing/Activities
== Testing Activities ==
'''Please head over [[https://wiki.ubuntu.com/Testing/Activities | Testing Activities Page]] for more information about our Testing Activities and possible test case scenarios'''.

== Use Raring ISOs ==

To save downloading the whole iso again for saucy, simply copy your raring image of what ever architecture replacing 'raring' with 'saucy' and use zsync. (You can, of course, simply do a '''mv''', but I like to keep my older iso's handy).

== Bugs ==

Please head over to '''[[https://wiki.ubuntu.com/QATeam/Overview/#Bugs | All about bugs]]''' for further information on how bug reporting works and why it is so important. Also, please see '''[[https://help.ubuntu.com/community/ReportingBugs | How to Report Bugs]]'''.


== Testing ==
Testing is split into distinct, but joined areas. The '''Daily Builds''', the '''QA-testing of Milestone releases''' and the '''Milestone releases''' themselves.

To not get overly complicated, think of it as that we have a [[https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule | schedule]] to keep to. A few days before a Milestone is due, the daily is plucked and becomes the QA (Quality Assurance) test version for the Milestone release. Once it is confirmed that the QA version works, it then becomes the [[https://wiki.ubuntu.com/UbuntuGNOME/Testing#Milestone_Releases | Milestone]].

All release stages are tracked by [[http://iso.qa.ubuntu.com/ | ISO Tracker]] where you can get the latest builds, see and allocate any Bugs.

So, in order of how they happen.

=== Daily Builds ===

These ISOs are automatically generated every 24 hours using the latest updates on the system from the developers. They are available from [[http://iso.qa.ubuntu.com/|ISO tracker]]. Using the [[https://help.ubuntu.com/community/ZsyncCdImage | zsync (or rsync)]] option allows you to update your [[https://help.ubuntu.com/community/BurningIsoHowto |iso]] to any of the various dailies you choose to follow without having to re-download the entire iso. They are there to check that bugs that are resolved between the Milestone releases do not break the install. They also are used to confirm that any fix for a bug that seriously affects an initial install which is released for testing now works. Daily builds are suspended when pre-milestone testing is being carried out (see below).

==== When do they build? ====

The Desktops are scheduled to start at 16:29 (UTC) and take approximately 90 minutes to complete

''Please note from the release team: Sure, as long as it's clear that it's subject to change - We're not intending to make any promises here. We won't change them around frivolously or anything but it's possible.''

The timing of the auto build of Ubuntu GNOME can be found [[http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/etc/crontab | here ]]. If you do notice that builds are not appearing as expected, please contact [[amjjawad]] to let him know or just drop an email to Ubuntu GNOME [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome | Mailing List]].

=== QA testing of Milestone releases ===

Cadence, Beta and Release Candidates (RC) are also tested using [[http://iso.qa.ubuntu.com/|ISO tracker]]. If you want to help out in this important area of testing, please read through [[https://wiki.ubuntu.com/Testing/ISO/Procedures | Procedures]] for further details. These appear a couple of days before the actual Milestone release so that we can check they are okay to become Milestone releases.

'''QA testing is to ensure the actual install iso works, if you can, please get involved in the qa testing'''

==== Rebuilding a Release Candidate ====

These are carried out manually, during this time the release team do update the [[http://iso.qa.ubuntu.com/qatracker | notice panel]]. Please ask on #ubuntu-release if you have questions.

=== Milestone Releases ===

Once a Milestone release passes the QA testing, it becomes a Milestone Release and is listed on the [[http://cdimage.ubuntu.com/ubuntu-gnome/releases/ | Releases]] as such.

If you would to know more about how this all works, have a read of [[https://wiki.ubuntu.com/QATeam/Overview/TheStages | Stages of testing]].


== General Testing ==
During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read [[http://ubuntuforums.org/showthread.php?t=1479146|Partial Upgrades]].

=== Known Issues ===
All the known issues for a particular release are mentioned in the Announcement email, and are available to see at [[http://iso.qa.ubuntu.com/ | ISO Tracker]].

=== Manual test of ISO and CD ===
On the help-pages of Ubuntu there is an extensive guide on [[https://help.ubuntu.com/community/HowToMD5SUM|how to MD5SUM]].

 
== Specific Testing ==

=== QA tests ===
You can do more specific tests, like ones done for the Ubuntu ISO : http://iso.qa.ubuntu.com/qatracker

=== Laptop Testing ===

Laptops never cease to have their little 'quirks'. You can help on this important area by heading over to [[https://wiki.ubuntu.com/Testing/Laptop/Procedures | Laptop Testing]] for full details.


=== Unwanted packages ===
Some packages can be automatically installed, but are not wanted on a default installation. To find the package which automatically installed the package that you don't want :
 * Install {{{apt-rdependsi}}}
 * run "{{{apt-rdepends -r --show=Depends the_unwanted_package}}}" => It will show which packages depend on {{{the_unwanted_package}}}.
 * Run "{{{apt-rdepends -r --show=Recommends the_unwanted_package}}}" => It will show which packages recommend {{{the_package_unwanted}}} (recommended packages are installed by default).
 * You may have to run the commands several times to see the complete chain of depends / recommends.

= See Also =
 * [[https://wiki.ubuntu.com/QATeam | Ubuntu QA Team Page]]
 * [[https://wiki.ubuntu.com/Testing/Activities | QA Activities Page]]
<<BR>>
== See Also ==
<<BR>>
||<tablestyle="width:95%;" style="width: 40px; padding-top: 0.5em; border: none; background-color: #ffffff;">{{attachment:IconsPage/iconCircle48.png}}||<style="width: 20%; border: none; font-size: 0.90em; background-color: #ffffff;" >[[QATeam| Ubuntu Quality Team]]||<style="border:none">||<style="width: 40px; padding-top: 0.5em; border: none; background-color: #ffffff;">{{attachment:IconsPage/picto_calendar_48.png}}||<style="width: 20%; border: none; font-size: 0.90em; background-color: #ffffff;" >[[QATeam/Hackfest|Hackfests & Calendar]]||<style="border:none">||<style="width: 40px; padding-top: 0.5em; border: none; background-color: #ffffff;">{{attachment:IconsPage/picto_locations_48.png}}||<style="width: 20%; border: none; font-size: 0.90em; background-color: #ffffff;" >[[QATeam/Roles|Roles]]||<style="border:none">||<style="width: 40px; padding-top: 0.5em; border: none; background-color: #ffffff;">{{attachment:IconsPage/picto_discussion_48.png}}||<style="width: 20%; border: none; font-size: 0.90em; background-color: #ffffff;" >[[https://wiki.ubuntu.com/QATeam/Contact|Contact]]||<style="border:none">||<style="width: 40px; padding-top: 0.5em; border: none; background-color: #ffffff;">{{attachment:IconsPage/picto_projects_we_love_48.png}}||<style="width: 20%; border: none; font-size: 0.90em; background-color: #ffffff;" >[[QATeam/FAQ|FAQ]]||
<<BR>><<BR>>

Testing



Bugs


Note: It is not uncommon for developers to request the Bug reporter to file the Bug upstream where relevant, obviously the actual reporter can usually provide more info, testing etc. That said, upstream Bugs should really only be submitted once an Ubuntu Developer has requested it.

Upstream GNOME Bugs


Testing Activities


  • For more information and details about Testing:

Please head over Testing Activities Page


See Also




UbuntuGNOME/Testing (last edited 2016-11-16 18:29:19 by awjinahn)