Test Day:2011-03-10 GNOME3 Beta

Click here to set up this language box

Fedora Test Days
GNOME 3 (pre-F15 Beta)
Date	2011-03-10
Time	all day
Website	http://www.gnome3.org
IRC	#fedora-test-day (webirc)
Mailing list	test

In construction
This page is still in construction, being rewritten from the previous test day page, and with the new set of test cases being developed right now. Please note that the very final version of this page might not be done until the test day itself (including all the latest DVD images etc.).

Can't make the date?
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 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.

Big changes ahead
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), Vitezslav Humpa (vhumpa)

Prerequisite for Test Day

• An updated Branched (tips on installing Branched/15 below), 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.

Unsupported adapters
Some adapters are known to be currently not working or problematic with the Shell. NVIDIA GeForce 400 series (Fermi / NVC0) adapters currently have no acceleration support and should fall back to compatibility mode (see the fallback testing section below). GeForce FX adapters may exhibit poor performance. Interaction may fail with GeForce 2 / GeForce 4 MX adapters, making the desktop effectively unusable.

Shell will not work in VirtualBox or virt-manager / KVM
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)
• Wi-fi/bluetooth enabled networking devices
• 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 Beta, you will need a latest updated Alfa installation or live image to perform the testing.

Live image

Getting the right Live image
The live images for the Test Day are in progress. The x86_64 and i686 images are uploaded now, but please check the SHA256SUM is correct before booting!

Post-live image updates

The following updates that fix known bugs are available beyond what is included in the live image: Using the live image is the easiest way to participate in testing for most people, but alternatively you can:

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

Regular tests

New in Beta Test Day

This is a new set of test cases aiming at more different parts of GNOME 3 that we think should be in order for the F15 Beta release.

• QA:Testcase_desktop_volume - rlat (this is just an internal divison on who'll write the test cases)
• QA:Testcase_desktop_network - rlat
• QA:Testcase_desktop_bluetooth - vhumpa
• QA:Testcase_desktop_non_gtk_apps - vhumpa
• QA:Testcase_desktop_message_notification - rlat
• QA:Testcase_desktop_gdm - rlat
• QA:Testcase_desktop_lock_screen - rlat
• QA:Testcase_desktop_packagekit - vhumpa
• QA:Testcase_desktop_terminal - vhumpa
• QA:Testcase_desktop_unicode - rlat/vhumpa
• QA:Testcase_brasero_image_burn - vhumpa
• QA:Testcase_wine_apps - vhumpa
• ...

Important tests from Alfa Test Day

These tests have been part of the previous GNOME 3 Test day, and need go through an another round of testing. Most of these were failed often with many users and we need to see whether the issues with these test have improved for the better since the previous Test day.

• QA:Testcase_desktop_uri - remove - NOTE: GNOME 3 does not provide a configuration interface for preferred applications, so skip that step; this is intended
• QA:Testcase_desktop_common_shortcuts - maybe remove
• QA:Testcase_desktop_date - keep - ERRATA: GNOME date/time config applet seems to crash on launch on live images, works on an installed desktop; may be a missing dependency
• QA:Testcase_desktop_keyring - maybe remove
• QA:Testcase_gnome-shell_dash - remove
• QA:Testcase_gnome-shell_overview_search - maybe keep
• QA:Testcase_gnome_desktop_background - remove
• QA:Testcase_generic_video_glx - remove
• QA:Testcase_generic_video_multihead - keep
• QA:Testcase_evince_file_display - remove (RHBZ #[[rhbug:|]])
• QA:Testcase_firefox_browse - remove
• QA:Testcase_firefox_media - remove
• QA:Testcase_totem_basic - remove
• QA:Testcase_vino_vinagre_connect - maybe remove
• QA:Testcase_desktop_automount - keep - NOTE: there will be no file manager on the Desktop, see this mail for the design decision behind it
• QA:Testcase_desktop_menus - keep

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.

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	none	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	warn	fail
User	Smolt Profile	Fallback	URIs	Shortcuts	Date	Keyring	Dash	Search	Background	GL	Multihead	Evince	Browse	Web media	Totem	VNC	Mount	Menus	References