| Fedora Test Days | |
|---|---|
| |
| Gnome 3.6 | |
| Date | 2012-11-08 |
| Time | all day |
| Website | QA/Fedora_18_test_days |
| 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 instalment of Fedora Test Day will focus on Gnome 3.6.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Developer1 (irc_nick1), Developer2 (irc_nick2)
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), 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:
Live image
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases
Gnome Shell
- QA:Testcase Gnome Login Screen
- QA:Testcase Gnome Shell Activities
- QA:Testcase Gnome Lock Screen
- QA:Testcase Gnome Shell Software Rendering
- QA:Testcase Gnome Shell Extensions
- QA:Testcase Gnome Accessibility
- QA:Testcase Gnome Control Center
Gnome Applications
- QA:Testcase Gnome Web
- QA:Testcase Gnome Files
- QA:Testcase Gnome Online Accounts
- QA:Testcase Gnome Documents
- QA:Testcase Empathy
- QA:Testcase desktop message notification
- QA:Testcase Evolution
- QA:Testcase Gnome Boxes
- QA:Testcase Disk Usage Analyzer
- QA:Testcase Gnome Disks
- QA:Testcase Gnome Clocks
- QA:Testcase Gnome Font Viewer
Test Results
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 |
|---|---|---|---|---|---|---|
| Sample User | HW | |
 |
 |