Drinking our own champagne

Differences between revisions 15 and 24 (spanning 9 versions)
⇤ ← Revision 15 as of 2013-07-03 20:09:53 →
Size: 2965
Editor: adsl-98-70-135-150
Comment:
← Revision 24 as of 2013-08-12 19:39:58 → ⇥
Size: 2247
Editor: host-89-242-219-4
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from QATeam/Hackfest
Line 4: Line 5:
This page details information for hackfests. A hackfest is a gathering of interested contributors with the goal of contributing new testcases as well as fixing and enhancing existing testcases. Testcases are generally targeted for each hackfest, but all contributions are welcome. Members from the quality team make themselves available during the fests to help streamline contributions.
Line 6: Line 6:
== Upcoming Hackfests ==
Click the date linked below for the specific details on the hackfest.		 = Why use a development release for daily use =
||<tablestyle="font-size: 0.9em; margin: 0.5em;" style="padding:0.5em;">{{attachment:IconsPage/champagne_ubuntu.png}}||
Line 9: Line 9:
 * '''[[QATeam/Hackfest/20130705|July 5th, 2013]]''' from 1300 UTC - 1400 UTC
 * '''[[QATeam/Hackfest/20130709|July 9th, 2013]]''' from 1800 UTC - 1900 UTC
 * '''[[QATeam/Hackfest/20130711|July 11th, 2013]]''' from 2200 UTC - 2300 UTC		 This page details information for running the development release as a day to day system.
Whilst we have a good range of test cases that will pick up any issues with the standard installation, there is nothing like using a development system on a daily basis as if it was you production machine. That said, please do be aware that it may break on you and keeping regular backups is essential!
Line 13: Line 12:
==== Previous Hackfests ==== One example of such testing is a bug that affected kvm with the new kernel release [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204005 | kvm host hangs]], which was only picked up because it was installed onto a development release and caused a system freeze. We cannot write test cases for every possible application that you may install, so this is a great way to find this sort of issue.
Line 15: Line 14:
 * '''[[QATeam/Hackfest/20130703|July 3rd, 2013]]''' from 1800 UTC - 1900 UTC
 * '''[[QATeam/Hackfest/20130613|June 13th, 2013]]''' from 1200 UTC - 2000 UTC
 * '''[[QATeam/Hackfest/20130604|June 4th, 2013]]''' from 1200 UTC - 2000 UTC
 * '''[[QATeam/Hackfest/20130523|May 23rd, 2013]]''' from 1200 UTC - 2000 UTC
 * '''[[QATeam/Hackfest/20130319|March 19th, 2013]]''' from 1200 UTC - 2300 UTC
 * '''[[QATeam/Hackfest/20130201|Feb 1st, 2013]]''' all day
 * '''[[QATeam/Hackfest/20121213|December 13th, 2012]]''' all day		 = Updating a development release =

Whilst for production releases, it is normal to use:

{{{
sudo apt-get update
sudo apt-get upgrade
}}}

For development releases the command is slightly different:

{{{
sudo apt-get update
sudo apt-get dist-upgrade
}}}

It is also important that you are aware of the system offering partial updates, this is covered at [[http://ubuntuforums.org/showthread.php?t=1594833 | common questions for testing]].

= PPA usage =

It is normal that you may be asked to test a new version of something. The developers often hold these in a PPA. [[https://wiki.ubuntu.com/Lubuntu/Testing/PPA_Testing | PPA Testing]] has details on this. '''Be sure to only add a trusted ppa''', this will usually come via an email / announcement from the ubuntu-quality area. If you are ever in doubt, you '''must''' check.
Line 24: Line 37:
== Location ==
[[http://webchat.freenode.net/?channels=ubuntu-quality|#ubuntu-quality on freenode]]
Line 27: Line 38:
== How can I participate? ==
 * Click the date representing the hackfest of interest above and add yourself to hack on something
 * Show up on IRC during the scheduled time!
  * Even if your not writing tests, there's potential to help other test authors by validating, reviewing, cheerleading, providing feedback, etc
 * Review/Sponsor incoming test contributions

== How can I prepare? ==
First read and make sure your setup to contribute

[[https://wiki.ubuntu.com/QATeam/ContributingTestcases|Contributing Testcases]]

Then, for more information on contributing each type of test, check out the wiki links below to prepare yourself for the hackfest.

[[https://wiki.ubuntu.com/QATeam/AutomatedTesting/Hackfest|Automated Tests]]

[[https://wiki.ubuntu.com/QATeam/ManualTestingHackfest|Manual Tests]]

== What types of tests are being targeted? ==
Test contributions of all types (automated and manual, etc) are targeted during the hackfests. See the applicable hackfest page linked above under schedule for the specifics.

== What can I expect as part of the hackfest? ==
 * A opportunity to learn and get help with contributing tests of all types to ubuntu
 * Plenty of hugs from dholbach, balloons by balloons, a discussion on Australian vs British vs American English with thomi, and pitti's and jibel's discourses in french and german		 = What can I expect as part of being such a tester? =
 * A opportunity to learn lots and get help with testing.
 * Plenty of hugs from everyone on the quality team.

Why use a development release for daily use

IconsPage/champagne_ubuntu.png

This page details information for running the development release as a day to day system. Whilst we have a good range of test cases that will pick up any issues with the standard installation, there is nothing like using a development system on a daily basis as if it was you production machine. That said, please do be aware that it may break on you and keeping regular backups is essential!

One example of such testing is a bug that affected kvm with the new kernel release kvm host hangs, which was only picked up because it was installed onto a development release and caused a system freeze. We cannot write test cases for every possible application that you may install, so this is a great way to find this sort of issue.

Updating a development release

Whilst for production releases, it is normal to use: 

sudo apt-get update
sudo apt-get upgrade

For development releases the command is slightly different: 

sudo apt-get update
sudo apt-get dist-upgrade

It is also important that you are aware of the system offering partial updates, this is covered at common questions for testing.

PPA usage

It is normal that you may be asked to test a new version of something. The developers often hold these in a PPA. PPA Testing has details on this. Be sure to only add a trusted ppa, this will usually come via an email / announcement from the ubuntu-quality area. If you are ever in doubt, you must check.

What can I expect as part of being such a tester?

  • A opportunity to learn lots and get help with testing.
  • Plenty of hugs from everyone on the quality team.
  • Seriously, a good time!

QATeam/Drinking our own champagne (last edited 2013-08-12 19:39:58 by host-89-242-219-4)