|Fedora Test Days|
|Mail • Subscribe • Archives|
What to test?
Today's instalment of Fedora Test Day will focus on new features in Gnome 3.6.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Rui Matos (rtcm), Debarshi Ray (rishi), Bastien Nocera (hadess)
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Vladimír Beneš (vbenes), Adam Williamson (adamw)
Prerequisite for Test Day
- bootable USB key or CD/DVD disk with latest Fedora 18 live image or:
- machine or VM with updated Fedora 18
- An updated Fedora F18 pre-release or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
This Test Day has two parts. First part is covered by test cases and it's focused on initial setup and getting you familiar with basic functionality. Second is exploratory testing when you are free to use software how do you like. Don't worry and try to break Gnome in various ways which you expect to work.
Update your machine
If you're running Fedora F18, make sure you have all the current updates for it installed, using the update manager. Or:
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Computers with obsolete graphics with buggy 3D drivers and VM hypervisors like KVM or VirtualBox don't have complete 3D support yet. But you can run Gnome Shell using software rendering (llvmpipe driver) on the CPU.
- You may need to uninstall your GPU driver by running
yum remove xorg-x11-drv-nouveaufor example to force enable llvmpipe driver. You will need to restart X by logging out and back in for this to take effect.
- Of lesser interest, but still worth checking, is whether GPUs already on the hardware blacklist work with their native driver instead. This can be checked by commenting out the appropriate entry from
/usr/share/gnome-session/hardware-compatibilityand logging out and back in to Gnome.
- System Settings
- Online Accounts - Google
- Online Accounts - Facebook
- Online Accounts - Windows Live
- Online Accounts - MS Exchange
- Online Accounts - Kerberos
- Empathy - Audio Call with Jabber
- Empathy - Video Call with Jabber
- Disk Usage Analyzer
- Font Viewer
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. 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 enter your result, as shown in the example result line.
|User||Smolt Profile||Sample test 1||Sample test 2||Sample test 3||Sample test 4||References|