Test Day:2011-03-10 GNOME3 Beta

What to test?
Today's installment of Fedora Test Day will focus on GNOME 3. This is the second 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.



Who's available
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
 * Development - Matthias Clasen (mclasen)
 * Quality Assurance - Adam Williamson (adamw), Vítězslav Humpa (vhumpa), Radek Lát (rlat)

Prerequisite for Test Day

 * An updated Fedora 15 pre-release, or the specific Test Day live image.
 * Your hardware profile uploaded to Smolt according to these instructions


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

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)
 * Wi-fi/bluetooth enabled networking devices
 * Graphics adapters, virtual machines, or driver configurations not capable of compositing, to test fallback support (see below)

Live image
You may download a non-destructive pre-Fedora 15 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Note that these 2 images are not CD-sized so should be used either on a DVD or a thumb drive.

Using the live image is the easiest way to participate in testing for most people, but alternatively you can:

Update your machine to Fedora 15
If you are already running or want to try the pre-release of Fedora 15, install Fedora 15 Alpha and then update to the latest packages. As of 2011-03-09, all the necessary packages for the Test Day should be available in the fedora or updates-testing repositories. Using the live image is easier and highly recommended.

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

 * QA:Testcase_gnome3_fallback

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, and leave the other test columns empty.

Desktop test set
These test are targeted at the new desktop environment, probing areas specific to the new GNOME 3 itself.


 * QA:Testcase_desktop_uri NOTE: Use System Settings -> System Info -> Default Applications to configure your preferred applications
 * QA:Testcase_desktop_common_shortcuts
 * QA:Testcase_desktop_date
 * QA:Testcase_desktop_keyring
 * QA:Testcase_desktop_volume
 * QA:Testcase_desktop_non_gtk_apps
 * QA:Testcase_desktop_message_notification
 * QA:Testcase_desktop_lock_screen
 * QA:Testcase_desktop_automount NOTE: there will be no file manager on the Desktop, see this mail for the design decision behind it
 * QA:Testcase_desktop_menus
 * QA:Testcase_desktop_login
 * QA:Testcase_generic_video_glx
 * QA:Testcase_generic_video_multihead

Application specific test set
Following are tests that focus on specific applications that are an important part of the default GNOME 3 experience. Please note that these are of the same importance for GNOME as previous ones. This separation addresses primarily just the issue of single results table size.


 * QA:Testcase_brasero_burn


 * QA:Testcase_gnome-bluetooth_send_file
 * QA:Testcase_gnome-shell_dash
 * QA:Testcase_gnome-shell_overview_search
 * QA:Testcase_gnome_desktop_background
 * QA:Testcase_evince_file_display
 * QA:Testcase_firefox_browse
 * QA:Testcase_firefox_media
 * QA:Testcase_totem_basic
 * QA:Testcase_gnome-terminal_profile
 * QA:Testcase_vino_vinagre_connect

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.

NOTE: There are updated control-center packages if you experience crashes in the "Region and Language" panel

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.