No edit summary |
|||
| Line 146: | Line 146: | ||
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. | 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 | ! User | ||
| Line 210: | Line 211: | ||
! References | ! References | ||
|} | |} | ||
--> | |||
[[Category:Fedora 15 Test Days]] | [[Category:Fedora 15 Test Days]] | ||
Revision as of 17:41, 27 February 2011
| 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 |
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.).
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.
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 for testing, workarounds, bug fixes, and general discussion ...
- Development - Matthias Clasen (mclasen)
- Quality Assurance - Adam Williamson (adamw)
Prerequisite for Test Day
- An updated pre-release of Fedora 15 (tips on installing Branched/FC15 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.
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.
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
The live images for the Test Day are in progress. The x86_64 and i686 images are will be uploaded for the Test day itself, but please check the SHA256SUM is correct before booting!
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.
| Architecture | SHA256SUM | |
|---|---|---|
| i686 | European Mirror | to-be-done |
| x86_64 | European Mirror | to-be-done |
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:
Update your machine to Fedora 15
If you want to try the pre-release of Fedora 15, see the instructions on the Branched page on the various ways in which you can install or update to Fedora 15. 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
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
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: GNOME 3 does not provide a configuration interface for preferred applications, so skip that step; this is intended
- QA:Testcase_desktop_common_shortcuts
- QA:Testcase_desktop_date 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
- QA:Testcase_desktop_volume - rlat (this is just an internal divison on who'll write the test cases)
- QA:Testcase_desktop_non_gtk_apps - vhumpa
- QA:Testcase_desktop_message_notification - rlat
- QA:Testcase_desktop_lock_screen - rlat
- QA:Testcase_desktop_unicode - rlat/vhumpa (maybe we can drop this, since we have three l18n/l10n test days coming...)
- 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 - rlat (the Warning might be removed as it is no longer relevant)
- 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.
- QA:Testcase_brasero_burn - vhumpa
- QA:Testcase_wine_apps - vhumpa
- QA:Testcase_gnome-bluetooth_send_file - vhumpa
- QA:Testcase_NM_applet - rlat
- 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 - vhumpa
- 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.