Testing

Differences between revisions 3 and 104 (spanning 101 versions)
Revision 3 as of 2013-07-22 14:23:38
Size: 7675
Editor: amjjawad
Comment:
Revision 104 as of 2016-11-16 18:27:36
Size: 4392
Editor: awjinahn
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
COMING SOON! <<Include(UbuntuGNOME/Header)>>
Line 3: Line 3:
'''Go Back to [[https://wiki.ubuntu.com/UbuntuGNOME | Home Page]]''' ||<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; line-height: 200%;"><<TableOfContents>>||
Line 7: Line 7:
= Testing Ubuntu GNOME = = 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 9: Line 11:
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 11: Line 13:
||<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 12: Line 15:
'''13.10 Alpha 1 has now been released, we are now back on the dailies.''' ||<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 14: Line 17:
For Ubuntu GNOME Saucy Daily Build, please see [[http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/ | this]]. <<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 16: Line 22:
##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. ||<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 18: Line 24:
##Please read the [[https://wiki.ubuntu.com/SaucySalamander/Alpha1/Lubuntu | release notes for Alpha 1]].
##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 21: Line 26:
<<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 32:

== Use Raring iso's ==

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).


== Getting Involved ==

Please do join our [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome | Mailing List]] and 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.

##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.

== 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.


== 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/Lubuntu/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 [[https://wiki.ubuntu.com/Lubuntu/ReportingBugs | Bugs]].

So, in order of how they happen.

=== Daily Builds ===

These iso's are automatically generated every 24 hours using the latest updates on the system from the devs. 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 Alternates are scheduled to start at 16:29 (UTC) and take approximately 30 - 45 minutes to complete.

The Desktops are also kicked off at this time, but take approximately 90 minutes to complete.

The armfh-ac100 is started at 01:35 (UTC) and should take approximately 30 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 lubuntu 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 [[phillw]] to let him know.

=== 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/lubuntu/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]]. In our case the terminal would be [[https://wiki.ubuntu.com/Lubuntu/DocumentationHelp/LXTerminal| LXTerminal]].

 
== 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-rdepends
 * 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.
<<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)