Test Day:2012-11-15 KDE 4.9

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Created page with "{{Infobox_group | name = Fedora Test Days | image = link=QA/Fedora_18_test_days | caption = FIXME | date = <<FIXME>> | time = all day ...")
 
Line 14: Line 14:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
+
Today's instalment of Fedora Test Day will focus on KDE Plasma Workspaces
  
 
== Who's available ==
 
== Who's available ==
  
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+
* Development - [[User:Ltinkl|Lukáš Tinkl]] (ltinkl), [[User:Rdieter|Rex Dieter]] (rdieter), [[JaroslavReznik|Jaroslav Řezník]] (jreznik), [[User:Kkofler|Kevin Kofler]] (Kevin_Kofler), [[User:Than|Than Ngo]] (than)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+
* Quality Assurance - [[User:Martix|Martin Holec]] (Martix), [[User:Vhumpa|Vítězslav Humpa]] (vhumpa), [[User:Adamwill|Adam Williamson]] (adamw)
  
 
== Prerequisite for Test Day ==  
 
== Prerequisite for Test Day ==  
  
List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+
* Use image linked below, or an updated [http://fedoraproject.org/get-prerelease Fedora 18 pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
 +
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
  
* Usb key
+
Also helpful, if you have or can get them:
* Usb externally connected HD IDE/SATA
+
* Additional displays (monitors, TVs...) for testing multihead setup
* Empty HD IDE/SATA/SCSI
+
* Wi-fi/bluetooth enabled networking devices
* Free space on HD
+
* Graphics adapters, virtual machines, or driver configurations not capable of compositing
  
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
+
== How to test? ==
  
* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
+
Boot latest Fedora 18 into KDE 4.8 Plasma Workspaces.
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
+
  
== How to test? ==
+
==== Live image ====
  
High level details on how a contributor can get involved.  This can include (but not limited to):
+
{{admon/important|Verification|Please check the SHA256SUM is correct before booting!}}
  
* Areas to target with exploratory testing
+
You may download a non-destructive pre-Fedora 18 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
* A list of pre-defined test cases to execute
+
* How to report back results
+
  
Here's another common chunk (again, replace XX as above):
+
{|
 +
!colspan=1|Architecture !! SHA256SUM
 +
|-
 +
|  || <code></code>
 +
|-
 +
|  || <code></code>
 +
|-
 +
|}
  
=== '''Update your machine''' ===
+
{{admon/important|Updating Live system|
 +
Do not attempt to run ''yum update'' it may break your running Live system. RHBZ [[https://bugzilla.redhat.com/show_bug.cgi?id=741594 #741594]]}}
  
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+
{{admon/important|Running in KVM|
 +
Due to known rendering problem, use QLX/Spice video option. If you're unsure how to set it up properly, ping us at #fedora-test-day. RHBZ [[https://bugzilla.redhat.com/show_bug.cgi?id=810161 #810161]]}}
  
=== '''Live image''' ===
+
Using the live image is the easiest way to participate in testing for most people, but alternatively you can:
  
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+
==== Update your machine to Fedora 18 ====
  
== Test Cases ==
+
If you are already running or want to try the pre-release of Fedora 18, [http://fedoraproject.org/get-prerelease install Fedora 18 Alpha] and then update to the latest packages.
  
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]].
+
== 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 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.
 +
 
 +
Basic desktop usage:
 +
* [[QA:Testcase KDE4 Desktop Effects]] (by default)
 +
* [[QA:Testcase KDE4 Theming]] (KDM/KSplashX/Plasma-desktop)
 +
* [[QA:Testcase KDE4 GDM Integration]] (GDM integration, optional)
 +
* [[QA:Testcase KDE4 Session management]]
 +
* [[QA:Testcase KDE4 Applets/Plasmoids]]
 +
 
 +
Hardware integration:
 +
* [[QA:Testcase KDE4 Bluetooth]]
 +
* [[QA:Testcase KDE4 NM applet]]
 +
* [[QA:Testcase KDE4 device notifier applet]]
 +
* Volume applet (kmix)
 +
* [[QA:Testcase KDE4 battery applet]]
 +
 
 +
Essential apps:
 +
* kdepim
 +
* calligra
 +
* kde-telepathy
 +
* apper
 +
 
 +
Other features:
 +
* working sound in Phonon, esp. with regards to the PA and GStreamer integration
 +
* [[QA:Testcase KDE4 System Settings RootOnly Modules]] ("root" modules in System Settings)
 +
 
 +
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 [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] before you file a bug.
  
 
== Test Results ==
 
== 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, try and report a bug. Bugs clearly related to KDE Plasma Workspaces and it's rendering should be reported to [https://bugs.kde.org/ KDE Bugzilla]. Bugs that are clearly issues in Fedora KDE integration should be reported to [http://bugzilla.redhat.com Fedora Bugzilla]. If you are unsure, please report into [http://bugzilla.redhat.com 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://irc.freenode.net/#fedora-test-day IRC].
 +
 
 +
If you are not sure of the appropriate component), please check in [irc://irc.freenode.net/#fedora-test-day 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://irc.freenode.net/#fedora-test-day IRC] and we will help you.
  
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
+
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.
  
 
{|
 
{|

Revision as of 09:44, 8 November 2012

Fedora Test Days
Echo-testing-48px.png
FIXME

Date <<FIXME>>
Time all day

Website QA/Fedora_18_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 Workspaces

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

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 18 into KDE 4.8 Plasma Workspaces.

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
Important.png
Updating Live system
Do not attempt to run yum update it may break your running Live system. RHBZ [#741594]
Important.png
Running in KVM
Due to known rendering problem, use QLX/Spice video option. If you're unsure how to set it up properly, ping us at #fedora-test-day. RHBZ [#810161]

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 are already running or want to try the pre-release of Fedora 18, install Fedora 18 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 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.

Basic desktop usage:

Hardware integration:

Essential apps:

  • kdepim
  • calligra
  • kde-telepathy
  • apper

Other features:

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
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345