Test Day:2013-03-14 KDE 4.10

From FedoraProject

Revision as of 10:44, 14 March 2013 by Lbrabec (Talk | contribs)

Jump to: navigation, search
Fedora Test Days
Echo-testing-48px.png
KDE 4.10

Date 2013-03-14
Time all day

Website QA/Fedora_19_test_days
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


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.

Contents

What to test?

Today's instalment of Fedora Test Day will focus on KDE Plasma Workspace 4.10 new features and general stability. Including Plasma Desktop, KDE Applications and 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 19 prerelease and if you want, install it on your computer.
  • Or update your current Fedora 17 or 18 machine from updates-testing.

Also helpful, if you have or can get them:

  • Additional displays (monitors, TVs...) for testing KScreen (multihead) setup
  • Wi-Fi/Bluetooth enabled networking devices
  • Printer
  • 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 19 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM
[ x86_64] waiting for build
[ i686] waiting for build

Using the live image is the easiest way to participate in testing for most people, but alternatively you can:

Update your Fedora 17 or 18 machine to KDE 4.10

KDE platform in Fedora follows rolling release model. That means you will eventually get KDE 4.10 via regular updates for your Fedora stable release. We want to ensure this transitions will be smooth and won't break any critical use case. Test Day is an opportunity to test this update before it reaches stable updates.

yum groupupdate @kde-desktop --enablerepo=updates-testing

Perform testing

Boot latest Fedora 19 into KDE 4.10 Plasma Workspaces or reboot your Fedora 17/18 machine after update.

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 Release Desktop Effects KWin GDM Integration Session management Applets/Plasmoids Accessibility Kickoff menu References
Sample User Fedora 19
none
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
pschindl Fedora 18
Inprogress inprogress
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
lbrabec Fedora 18
Pass pass
none
none
none
none
none
none

Hardware integration

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

KDE Applications

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

KDE Applications Extras

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