From Fedora Project Wiki

No edit summary
No edit summary
Line 139: Line 139:
| {{result|none}}  
| {{result|none}}  
| {{result|pass}}  
| {{result|pass}}  
| {{result|none}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Revision as of 12:42, 15 November 2012

Fedora Test Days
Echo-testing-48px.png
KDE 4.9

Date 2012-11-15
Time all day

Website QA/Fedora_18_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
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 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 ...

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

Important.png
Verification
Please check the SHA256SUM is correct before booting!

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
x86_64 b5610c6e6de8cc832f6e2971516541ba9b5939f139a5d9435c65803d05dd55f7
i686 624e7a6daeae7737297307b99507ec43f9b90db6f5f669c5a2568d2154bb8895

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

This time we don't have any packages included in the live image that are not yet present in updates-testing. Thus if you have already installed Fedora 18 pre-release, you can simply update to the latest packages (and yum install @kde-desktop-environment :) ).

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

Hardware integration

KDE Applications

KDE Applications Extras

Note.png
This is a list of applications which doesn't have written test cases. Feel free to test them on your own and have some fun while exploring new features!
  • KDE Partition Manager
  • Kontact
  • KMail
  • Juk
  • Kstars
  • Marble
  • KDE Games

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.

KDE desktop

User Desktop Effects GDM Integration Session management Applets/Plasmoids Accessibility Kickoff menu References
Sample User
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
mkrizek
Pass pass
none
none
Pass pass
none
Pass pass
Filip Holec
Warning warn [1] [2]
none
Pass pass
Pass pass
none
none
  1. RHBZ #876913
  2. RHBZ #876918

Hardware integration

User Bluetooth Multihead Printer KMix Battery applet References
Sample User
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345

KDE Applications

User Rekonq Calligra Suite KDE IM Apper Dolphin Okular Konsole References
Sample User
none
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
mkrizek
Pass pass
none
none
Pass pass
Pass pass
none
Pass pass

KDE Applications Extras

KDE Partition Manager Kontact KMail Juk Kstars Marble KDE Games References
Sample User
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345