RunTheDevelopmentVersion
|
Size: 912
Comment:
|
Size: 2740
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| 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. | ## page was copied from QATeam/Drinking our own champagne ## page was copied from QATeam/Hackfest <<Include(QATeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 3: | Line 6: |
| == Schedule == Our next hackfest will occur on: * Potentially, March 19th, 2013 from 1200 UTC - 2300 UTC |
= Drinking our own champagne = |
| Line 7: | Line 8: |
| == What types of tests are being targetted? == Both manual and automated test contributions are being targeted during the fest. For more information on contributing each type of test, check out the wiki links below to prepare yourself for the hackfest. |
This page details information for running the development release as a day to day system. |
| Line 10: | Line 10: |
| [[Automated Tests | https://wiki.ubuntu.com/QATeam/AutomatedTesting/Hackfest]] [[Manual Tests | https://wiki.ubuntu.com/QATeam/ManualTestingHackfest]] |
=== Why Drinking our own champagne? === Using your own system to test your own system is a mark of faith in that system. It is also known as ''dogfooding'' named after the dog food reps who would actually eat the dog food to show it was of good quality. ''icecreaming'' is another term and it comes loosely under the title of ''smoke testing''. As ubuntu produces the finest quality of operating system, why should we not ''drink our own champagne'' to show to everyone that ubuntu posses the ability to self test. = Why use a development version for daily use = 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 [[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. = 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. = 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! |
Drinking our own champagne
This page details information for running the development release as a day to day system.
Why Drinking our own champagne?
Using your own system to test your own system is a mark of faith in that system. It is also known as dogfooding named after the dog food reps who would actually eat the dog food to show it was of good quality. icecreaming is another term and it comes loosely under the title of smoke testing. As ubuntu produces the finest quality of operating system, why should we not drink our own champagne to show to everyone that ubuntu posses the ability to self test.
Why use a development version for daily use
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/RunTheDevelopmentVersion (last edited 2013-07-25 23:31:35 by host-2-99-156-185)