Testing
|
Size: 3821
Comment:
|
← Revision 38 as of 2015-07-28 21:25:13 ⇥
Size: 4803
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Testing is split into 3 main parts. | = Preparing for the Session = '''If you are interested in testing, also consider testing snappy. Checkout the [[Jams/Snappy|snappy jam page]] for more information.''' |
| Line 6: | Line 7: |
| 1. Image Testing. 1. Application Testing 1. Hardware Testing |
== Session Host == You are encouraged to familiarize yourself with performing the testing in advance so you have a basic understanding of what to expect. This is best done by performing a test yourself before the day of the jam. |
| Line 10: | Line 10: |
| = Testing Descriptions = The following descriptions can be used to help people decide how they want to participate. |
It is recommended you perform testing on the development version of ubuntu during the jam. To do this, you will be booting a live session of the development version of ubuntu and testing applications. Additionally you may perform an installation of the development version on real hardware or in a virtual machine. |
| Line 13: | Line 12: |
| == Image Testing == | == Participants == Have participants come prepared with a laptop and usb key (2 gb or greater) that can be wiped clean. |
| Line 15: | Line 15: |
| Image or iso testing consists of downloading a copy of the latest daily ISO images, burning them to CDs/USB keys (or loading them into VM's) and testing them. This brings to light many issues that might have been missed by other early adopters and developers, especially in the CD builds and installers. | * Ensure they have a [[https://help.launchpad.net/YourAccount/NewAccount|Launchpad/Ubuntu SSO account]] * Bring a laptop * Bring a usb key (2 gb or greater) * Ask them to download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest image]] * ''Optionally, if they have a ubuntu phone device, bring it!'' |
| Line 17: | Line 21: |
| == Application Testing == Application testing is the manual testing of specific things (test cases) in applications. Regression tests are specific tests for potential breakages from one release to another (they're also relevant for SRU testing, above). == Hardware Testing == Hardware Testing is about the manual testing of specific things (test cases) mainly related to laptops hardware. The goal is to get Ubuntu to work great on as many different makes and models of laptops as possible and this can be done knowing which hardware works straight off the install CD and which hardware needs configuring or is poorly supported. = Requirements = A computer.<<BR>> A Launchpad Account.<<BR>> An image of the current daily development version of ubuntu<<BR>> A network connection.<<BR>> Finally a virtual machine, such as KVM/Qemu/Virtualbox, unless installing on hardware. == Asking people to prepare for the Jam == Download a [[http://cdimage.ubuntu.com/daily-live/current/|copy of the latest iso]]<<BR>> === Material === Important links:<<BR>> [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]]<<BR>> [[http://packages.qa.ubuntu.com/ | The Package Tracker.]]<<BR>> [[http://laptop.qa.ubuntu.com/ | The Hardware Tracker.]]<<BR>> [[Testing/VirtualBox | Using VirtualBox (older version but works pretty much the same now).]]<<BR>> [[Testing/Automation/KVM | Towards the bottom half of the page gives you the general idea for a kvm command.]]<<BR>> |
You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them. |
| Line 47: | Line 24: |
| You are encouraged to perform each type of testing in advance so you have a basic understanding of what to expect. In addition, it's encouraged for you to read the following pages: | == Setup == Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu. |
| Line 49: | Line 27: |
| https://wiki.ubuntu.com/Testing/QATracker | [[https://wiki.ubuntu.com/QATeam/DevelopmentSetup|Follow the guide]] to ensure each participant has valid a bootable usb stick. Should this cause issues, follow the guide for virtualbox and have them test in a virtual machine. |
| Line 51: | Line 29: |
| https://wiki.ubuntu.com/Testing/Activities | If possible participants should try to test both the installation and the desktop / applications. If participants are unwilling or unable to test the installation, they can focus on testing the desktop instead inside a live session. |
| Line 53: | Line 31: |
| For each of the different types of testing a ubuntu global jam milestone should be setup on each tracker with the testcases ready to and and results ready to be reported against. | If / when you find an issue, please be sure and [[https://help.ubuntu.com/community/ReportingBugs|file a bug for it]]! |
| Line 55: | Line 33: |
| Note that unless folks are willing to do installations (via VM or real hardware) they will be testing using the live session of the image they brought with them (by booting it up into a VM or on real hardware) | == Testing == Boot the image and be sure to select the option allowing you to try ubuntu/xubuntu/kubuntu/lubuntu, etc. This will boot into a live session of the default desktop. |
| Line 57: | Line 36: |
| == Introduction Session == Provide an overview of each type of testing and let folks know they can choose to do any or all of the different types during the jam. |
Once booted into a live session, you are ready to test. Start by performing the application testing below. Once you've completed testing the application testing, it's time to try an install. See the image testing below for this final step. Optionally, participants can chose to try out unity8 and test it on there machine. |
| Line 61: | Line 41: |
| NOTE: Ubuntu global jam is a milestone, just like cadence testing. Thus the tutorial can be followed. [[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|https://wiki.ubuntu.com/Testing/Cadence/Walkthrough]] |
Testcases to execute: [[http://packages.qa.ubuntu.com/|Application Testcases]] Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily'). |
| Line 64: | Line 45: |
| === Install Testing === Follow the guide here: [[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|https://wiki.ubuntu.com/Testing/ISO/Walkthrough]] |
What is it?: Application testing is the manual testing of specific things (test cases) in applications. |
| Line 68: | Line 47: |
| === Hardware Testing === Boot your hardware up into a Live session, then follow: [[https://wiki.ubuntu.com/Testing/Laptop/Procedures|https://wiki.ubuntu.com/Testing/Laptop/Procedures]] |
What's tested?: The default desktop applications |
| Line 72: | Line 49: |
| == Tools & Helpful Information == | Tutorials: [[https://wiki.ubuntu.com/Testing/Cadence/Walkthrough|Application Testing Walkthrough]] |
| Line 74: | Line 52: |
| Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]]. | === Image Testing === Testcases to execute: [[http://iso.qa.ubuntu.com/|Image Testcases]] Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily'). What is it?: Image or iso testing consists of running through an installation of ubuntu. What's tested?: Iso image ubiquity / debian installer Tutorials: [[https://wiki.ubuntu.com/Testing/ISO/Walkthrough|ISO Testing walkthrough]] === Unity8 Testing === If you're adventurous and want to check out what the future of Ubuntu is going to hold, see [[Unity8Desktop]] for more information and help with testing Unity8. To file bugs, use the [[https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session|unity8-desktop-session]] package. The unity8 team will reassign your bug if necessary, please file bugs for any issues you find! === Phone Testing === Got a phone? Try living on the edge for a little while by trying out the development release for the weekend. Flash the [[https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/|devel-proposed channel]] and see what breaks! Although reflashing your phone won't cause you to lose data, make sure you have everything backed up before attempting this. == Important links == * [[QATeam/DevelopmentSetup | Testing Setup]] * [[http://iso.qa.ubuntu.com/ | The Iso Tracker.]] * [[http://packages.qa.ubuntu.com/ | The Package Tracker.]] == Getting Help == Get help on [[http://webchat.freenode.net/?randomnick=1&channels=ubuntu-quality|#ubuntu-quality]] on freenode. |
Preparing for the Session
If you are interested in testing, also consider testing snappy. Checkout the snappy jam page for more information.
Session Host
You are encouraged to familiarize yourself with performing the testing in advance so you have a basic understanding of what to expect. This is best done by performing a test yourself before the day of the jam.
It is recommended you perform testing on the development version of ubuntu during the jam. To do this, you will be booting a live session of the development version of ubuntu and testing applications. Additionally you may perform an installation of the development version on real hardware or in a virtual machine.
Participants
Have participants come prepared with a laptop and usb key (2 gb or greater) that can be wiped clean.
Ensure they have a Launchpad/Ubuntu SSO account
- Bring a laptop
- Bring a usb key (2 gb or greater)
Ask them to download a copy of the latest image
Optionally, if they have a ubuntu phone device, bring it!
You may wish to have extra usb keys already loaded with the proper image in case folks have trouble creating them.
Holding the Session
Setup
Let folks know they will be helping test there hardware and looking for bugs in the development version of ubuntu.
Follow the guide to ensure each participant has valid a bootable usb stick. Should this cause issues, follow the guide for virtualbox and have them test in a virtual machine.
If possible participants should try to test both the installation and the desktop / applications. If participants are unwilling or unable to test the installation, they can focus on testing the desktop instead inside a live session.
If / when you find an issue, please be sure and file a bug for it!
Testing
Boot the image and be sure to select the option allowing you to try ubuntu/xubuntu/kubuntu/lubuntu, etc. This will boot into a live session of the default desktop.
Once booted into a live session, you are ready to test. Start by performing the application testing below. Once you've completed testing the application testing, it's time to try an install. See the image testing below for this final step.
Optionally, participants can chose to try out unity8 and test it on there machine.
Application Testing
Testcases to execute: Application Testcases Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').
What is it?: Application testing is the manual testing of specific things (test cases) in applications.
What's tested?: The default desktop applications
Tutorials: Application Testing Walkthrough
Image Testing
Testcases to execute: Image Testcases Choose the current development version of ubuntu as the 'milestone'. (Currently that is 'vivid daily').
What is it?: Image or iso testing consists of running through an installation of ubuntu.
What's tested?: Iso image ubiquity / debian installer
Tutorials: ISO Testing walkthrough
Unity8 Testing
If you're adventurous and want to check out what the future of Ubuntu is going to hold, see Unity8Desktop for more information and help with testing Unity8.
To file bugs, use the unity8-desktop-session package. The unity8 team will reassign your bug if necessary, please file bugs for any issues you find!
Phone Testing
Got a phone? Try living on the edge for a little while by trying out the development release for the weekend. Flash the devel-proposed channel and see what breaks! Although reflashing your phone won't cause you to lose data, make sure you have everything backed up before attempting this.
Important links
Getting Help
Get help on #ubuntu-quality on freenode.
Jams/Testing (last edited 2015-07-28 21:25:13 by 1)