(revise results section) |
(re-order tests) |
||
| Line 78: | Line 78: | ||
=== Regular tests === | === Regular tests === | ||
* [[QA:Testcase_desktop_uri]] | * [[QA:Testcase_desktop_uri]] | ||
* [[QA:Testcase_desktop_common_shortcuts]] | * [[QA:Testcase_desktop_common_shortcuts]] | ||
* [[QA:Testcase_desktop_date]] | * [[QA:Testcase_desktop_date]] | ||
* [[QA:Testcase_desktop_keyring]] | |||
* [[QA:Testcase_gnome-shell_dash]] | * [[QA:Testcase_gnome-shell_dash]] | ||
* [[QA:Testcase_gnome-shell_overview_search]] | * [[QA:Testcase_gnome-shell_overview_search]] | ||
| Line 94: | Line 92: | ||
* [[QA:Testcase_totem_basic]] | * [[QA:Testcase_totem_basic]] | ||
* [[QA:Testcase_vino_vinagre_connect]] | * [[QA:Testcase_vino_vinagre_connect]] | ||
* [[QA:Testcase_desktop_automount]] | |||
* [[QA:Testcase_desktop_menus]] | |||
=== Unplanned testing === | === Unplanned testing === | ||
Revision as of 09:46, 3 February 2011
| Fedora Test Days | |
|---|---|
| |
| GNOME 3 (pre-F15 Alpha) | |
| Date | 2011-02-03 |
| Time | all day |
| Website | http://www.gnome3.org |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's installment of Fedora Test Day will focus on GNOME 3. This is the first of three Fedora 15 Test Days focusing on GNOME 3. The goal of these events is to test as much as possible of the functionality of GNOME 3 to ensure that it works correctly and provides the necessary basic features for a day-to-day usable desktop.
Remember, this ain't your momma's GNOME - the overall user experience of GNOME 3 is very different from GNOME 2. It's fine to ask about the changes and make feature requests, but before filing a bug on something that's 'missing' from GNOME 2, please ask in #fedora-test-day to make sure it's not an intended change. There should always be someone there who can answer your question. Thanks!
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Matthias Clasen (mclasen)
- Quality Assurance - Adam Williamson (adamw)
Prerequisite for Test Day
The live image that will be used on the test day is still being built. To perform the tests against current code, you will need an installed rawhide machine that you can update to the latest packages, or wait for the correct live CD to become available! Current Rawhide is also not up-to-date enough, there are some specific extra packages you'll need: instructions coming later.
- An updated Rawhide (tips on installing Rawhide below), or the specific Test Day Live CD Image.
- Your hardware profile uploaded to Smolt according to these instructions
Is smolt crashing or otherwise not working in Rawhide? A temporary fix is available to address bug#673015. Packages are available in the koji build system. To upgrade the
smolt package(s), with root permissions, type:
yum update "http://koji.fedoraproject.org/koji/getfile?taskID=2745512&name=smolt-1.4.3-2.jlaska.fc15.noarch.rpm" \ "http://koji.fedoraproject.org/koji/getfile?taskID=2745512&name=smolt-firstboot-1.4.3-2.jlaska.fc15.noarch.rpm" \ "http://koji.fedoraproject.org/koji/getfile?taskID=2745512&name=smolt-gui-1.4.3-2.jlaska.fc15.noarch.rpm"
- For most testing, a graphics adapter capable of compositing: we are aiming to support all NVIDIA GeForce adapters, all Intel adapters except for GMA 500 (Poulsbo) and pre-i915 (i8xx) adapters, and all ATI/AMD Radeon adapters. If you are using an unsupported adapter, you can still help us with fallback testing - see below.
Virtual machines without 3D acceleration pass-through support will not be suitable for most testing: the Shell will not run in these configurations. Also, even though some VirtualBox editions have passthrough support, the current Fedora implementation does not support it, so Shell will not work in VirtualBox either. If you are using a virtual machine, you can still help us with fallback testing - see below.
Also helpful, if you have or can get them:
- Additional displays (monitors, TVs...)
- As many storage devices as you can access
- Optical media (burned, commercially pressed, and blank burnable, CDs, DVDs and Blu-Rays)
- Graphics adapters, virtual machines, or driver configurations not capable of compositing, to test fallback support (see below)
How to test?
As this event comes before the release of Fedora 15 Alpha, you will need a Rawhide installation or live image to perform the testing.
Live image
The live image that will be used on the test day is still being built. To perform the tests against current code, you will need an installed rawhide machine that you can update to the latest packages, or wait for the correct live CD to become available!
You may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here. This is likely the easiest way to participate in testing for most people. Or:
Update your machine to Rawhide
If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. For now, you will also need to add a repository definition to /etc/yum.repos.d for the Koji Rawhide repo and update using that, as Rawhide proper does not yet have all the necessary packages. Using the live image, once it is available, is easier.
Perform testing
Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table.
Fallback testing
This test case will test that GNOME falls back correctly to a 'classic' environment if your hardware does not support the GNOME Shell. If your hardware starts GNOME Shell correctly, please leave the fallback test column empty, and fill in the other test result columns. If your hardware is unable to start GNOME Shell, but falls back correctly to a classic environment, please mark the fallback test in the results table as 'pass', and leave the other test columns empty. If your hardware is unable to start GNOME Shell, and does not fall back correctly to a classic environment, please mark the fallback test in the results table as 'fail', file a bug against 
gnome-session
Regular tests
- QA:Testcase_desktop_uri
- QA:Testcase_desktop_common_shortcuts
- QA:Testcase_desktop_date
- QA:Testcase_desktop_keyring
- QA:Testcase_gnome-shell_dash
- QA:Testcase_gnome-shell_overview_search
- QA:Testcase_gnome_desktop_background
- QA:Testcase_generic_video_glx
- QA:Testcase_generic_video_multihead
- QA:Testcase_evince_file_display
- QA:Testcase_firefox_browse
- QA:Testcase_firefox_media
- QA:Testcase_totem_basic
- QA:Testcase_vino_vinagre_connect
- QA:Testcase_desktop_automount
- QA:Testcase_desktop_menus
Unplanned testing
As well as running the formal test cases, you can help simply by running GNOME 3 and reporting any problems you come across in the course of your typical use, even if they do not match up with any of the test cases. Please remember, though, that just being different from GNOME 2 is not necessarily a problem, and check in #fedora-test-day before you file a bug.
Test Results
If you have problems with any of the tests, try and report a bug. Most bugs in this event should be reported to GNOME Bugzilla. Bugs that are clearly issues in Fedora GNOME integration should be reported to Fedora Bugzilla. You will need an account to report bugs, but creating one is easy, and we will help you do this if you ask in IRC.
If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to describe your result, following the examples in the Sample user row.
| User | Smolt Profile | Fallback | URIs | Shortcuts | Date | Keyring | Dash | Search | Background | GL | Multihead | Evince | Browse | Web media | Totem | VNC | Mount | Menus | References |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
 |
||
| User | Smolt Profile | Fallback | URIs | Shortcuts | Date | Keyring | Dash | Search | Background | GL | Multihead | Evince | Browse | Web media | Totem | VNC | Mount | Menus | References |