Get Involved/Quality

< Get Involved
Revision as of 13:17, 2 July 2012 by Mamarok (talk | contribs) (Existing testing tools)
Jump to: navigation, search


In the early 2000's there was a specific team at KDE which was focused on finding loose ends in KDE applications and tying them together. This was a task of user case studies, writing articles, documentation, creating missing artwork for consistency, and other miscellanea. Ultimately, this team contributed patches of code and documentation that really rounded out the KDE experience.

Early 2012 this team was revived and now has a mailing list as well as a channel called #kde-quality on

All domains where Quality is important are listed in this page: *

What exactly does testing mean?

Testing is part of the overall Quality Assurance of software. More information about the exact definition can be found here: and here:

A very interesting read is this:

Initial steps

Since this is a new start we need to define the exact goal of this team. There is a Brainstorming page where ideas are gathered.

Wiki work

The basics is of course to establish a useful wiki resource. We currently use to avoid duplicate work. Please ping Anne-Marie (annma) or Myriam (Mamarok) in #kde-quality on to be added to the group.

Trunk testing

Trunk testing can be done with Project Neon:

Beta testing

Please see the Beta subpage for more information.

Existing testing infrastructure

Continuous Integration (Jenkins)

KDE already runs a build server with Jenkins: Please ask the KDE sysadmins if you would like to use it for your project. Who gets the results? Who fixes them? This tool needs to be really used.

Unit tests

Tutorial for unit tests in KDE:

Code (syntax) tests

A static code analyzing tool is provided by the EnglishBreakfastNetwork.

Another static code analyzer is cppcheck which can be integrated with Jenkins.

More information can also be found here:

Coverity Prevent is another tool, not Open Source but we can get the results from it.


KDE already has an extensive wiki for debugging:

Existing testing tools

An non-exhaustive and maybe not up-to-date list of testing tools can be found here: See also

Name Description
QtTest Qt provides a testing module that can be used for unit testing: There also is a possibility to do basic UI testing.
Valgrind A tool to analyze memory leaks: All apps should be ran through Valgrind on a regular basis, part of the Quality Assurance.
Piglit A tool to test OpenGL drivers: might be useful to test parts of KWin and other OpenGL applications.
Gamma Ray A dynamic code analyzer: It is more a tool for developers to help them track down problems than a QA tool.
Testopia Testopia provides a test case management together with Bugzilla. This is currently evaluated by the KDE sysadmins: please be patient
Squish Not Open Source, but free 30 days triage
UI tests We will need to evaluate what tool would be the best for KDE. A list can be found here: (incomplete) and here:

ATP Examples

The following are examples for application testing procedures:

Application Test Procedure for Umbrello

Quality Guidelines

Plasma Applets:

Content is available under Creative Commons License SA 4.0 unless otherwise noted.