| Fedora Test Days | |
|---|---|
| |
| KDE Plasma Workspaces | |
| Date | 2012-04-10 |
| Time | all day |
| Website | QA/Fedora_17_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 KDE Plasma Workspaces
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Lukáš Tinkl (ltinkl), Rex Dieter (rdieter), Jaroslav Řezník (jreznik), Kevin Kofler (Kevin_Kofler)
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Adam Williamson (adamw)
Prerequisite for Test Day
- An updated Fedora 17 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
Also helpful, if you have or can get them:
- Additional displays (monitors, TVs...) for testing multihead setup
- Wi-fi/bluetooth enabled networking devices
- Graphics adapters, virtual machines, or driver configurations not capable of compositing
How to test?
Boot latest Fedora 17 into KDE 4.8 Plasma Workspaces.
Live image
Please check the SHA256SUM is correct before booting!
You may download a non-destructive pre-Fedora 17 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
| Architecture | SHA256SUM |
|---|---|
| [http:// x86_64] | TBD
|
| [http:// i386] | TBD
|
Do not attempt to run yum update it may break your running Live system. RHBZ [#741594]
Using the live image is the easiest way to participate in testing for most people, but alternatively you can:
Update your machine to Fedora 17
If you are already running or want to try the pre-release of Fedora 17, install Fedora 17 Alpha and then update to the latest packages.
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.
Regular tests
Here's a rough list of proposed test cases/areas:
Basic desktop usage:
- Desktop Effects by default
- QA:Testcase KDE4 Theming (KDM/KSplashX/Plasma-desktop)
- GDM integration
- QA:Testcase KDE4 Session management
- QA:Testcase KDE4 Applets/Plasmoids
Hardware integration:
- Bluetooth applet (bluedevil)
- Network Manager applet
- Device Notifier applet (removable media: optical, USB, encrypted)
- Volume applet (kmix)
- Battery applet (automatic profile switching, brightness)
Essential apps:
- kdepim
- calligra
- kde-telepathy
- apper
Unplanned testing
As well as running the formal test cases, you can help simply by running gnome-shell and reporting any problems you come across in the course of your typical usage of extensions, even if this does not match up with any of the test cases. If you are unsure to what any discovered problem relates, please check in #fedora-test-day before you file a bug.
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 |  |
 |
 |