Line 62: | Line 62: | ||
Here is the list of regular test. Some tests are optional as requires non-default settings and it's more difficult to set it up. The tests are divided into the four categories. | Here is the list of regular test. Some tests are optional as requires non-default settings and it's more difficult to set it up. The tests are divided into the four categories. | ||
==== KDE desktop ==== | |||
* [[QA:Testcase KDE4 Desktop Effects|Desktop Effects]] | |||
* [[QA:Testcase KDE4 GDM Integration|GDM Integration]] | |||
* [[QA:Testcase KDE4 Session management|Session management]] | |||
* [[QA:Testcase KDE4 Applets/Plasmoids|Applets/Plasmoids]] | |||
* [[QA:Testcase KDE4 Accessibility|Accessibility]] | |||
* [[QA:Testcase KDE4 KWin|KWin]] | |||
* [[QA:Testcase KDE4 Activities|Activities]] | |||
* [[QA:Testcase KDE4 Akonadi|Akonadi]] | |||
* [[QA:Testcase KDE4 Kickoff menu|Kickoff menu]] | |||
==== Hardware integration ==== | |||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Bluetooth|Bluetooth]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Multihead|Multihead]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Partition Manager|Partition Manager]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 KMix|KMix]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 battery applet|Battery applet]] | ||
==== KDE Applications ==== | |||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 IM|KDE IM]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Apper|Apper]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Dolphin|Dolphin]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Konsole|Konsole]] | ||
* [[QA:Testcase KDE4 | * [[QA:Testcase KDE4 Okular|Okular]] | ||
==== KDE Applications Extras ==== | |||
* | * [[QA:Testcase KDE4 Kontact|Kontact]] | ||
* | * [[QA:Testcase KDE4 KMail|KMail]] | ||
* | * [[QA:Testcase KDE4 Juk|Juk]] | ||
* | * [[QA:Testcase KDE4 Calligra Suite|Calligra Suite]] | ||
* [[QA:Testcase KDE4 Kstars|Kstars]] | |||
* [[QA:Testcase KDE4 Marble|Marble]] | |||
* | * [[QA:Testcase KDE4 KDE Games|KDE Games]] | ||
* [[QA:Testcase KDE4 | |||
Tests without a test case are more freeform tests - try the basic usage and let us know on IRC. The tests are not limited on these proposed, feel free to contact us with any problem you encountered during the Test Day (and even after Test Day on #fedora-kde channel). | Tests without a test case are more freeform tests - try the basic usage and let us know on IRC. The tests are not limited on these proposed, feel free to contact us with any problem you encountered during the Test Day (and even after Test Day on #fedora-kde channel). |
Revision as of 16:16, 13 November 2012
Fedora Test Days | |
---|---|
KDE 4.9 | |
Date | 2012-11-15 |
Time | all day |
Website | QA/Fedora_18_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's instalment of Fedora Test Day will focus on KDE Plasma Workspace 4.9. including Plasma Desktop and Netbook workspaces, the KDE Applications and the KDE Platform.
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), Than Ngo (than), Dan Vrátil (dvratil), Jan Grulich (jgrulich)
- Quality Assurance - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Vladimír Beneš (vbenes), Adam Williamson (adamw)
Prerequisite for Test Day
- Use live image linked below to boot Fedora 18 prerelease and if you want, install it on your computer.
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
Live image
You may download a non-destructive pre-Fedora 18 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Architecture | SHA256SUM |
---|---|
| |
|
Using the live image is the easiest way to participate in testing for most people, but alternatively you can:
Update your machine to Fedora 18
If you have already installed Fedora 18 prerelease, update to the latest packages.
Perform testing
Boot latest Fedora 18 into KDE 4.9 Plasma Workspaces.
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 is the list of regular test. Some tests are optional as requires non-default settings and it's more difficult to set it up. The tests are divided into the four categories.
KDE desktop
- Desktop Effects
- GDM Integration
- Session management
- Applets/Plasmoids
- Accessibility
- KWin
- Activities
- Akonadi
- Kickoff menu
Hardware integration
KDE Applications
KDE Applications Extras
Tests without a test case are more freeform tests - try the basic usage and let us know on IRC. The tests are not limited on these proposed, feel free to contact us with any problem you encountered during the Test Day (and even after Test Day on #fedora-kde channel).
Unplanned testing
As well as running the formal test cases, you can help simply by running KDE 4 Plasma Workspaces and reporting any problems you come across in the course of your typical usage of desktop, 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
If you have problems with any of the tests, try and report a bug. Bugs clearly related to KDE Plasma Workspaces and it's rendering should be reported to KDE Bugzilla. Bugs that are clearly issues in Fedora KDE integration should be reported to Fedora Bugzilla. If you are unsure, please report into Fedora Bugzilla or ask on #fedora-test-day or #fedora-qa. 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. If you are running Fedora in VM, please, at least state the name of VM hypervisor(kvm/VirtualBox...). However uploading Smolt profile is useful even for VMs. For each test case, use the result template to describe your result, following the examples in the Sample user row.
User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
---|---|---|---|---|---|---|
Sample User | HW |