< Get Involved
Revision as of 18:33, 5 April 2012 by Mamarok (talk | contribs) (added category, allowed menu)

Get Involved/Quality


Becoming a KDE Tester


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.

Communicating with the team

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

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: http://en.wikipedia.org/wiki/Software_quality_assurance and here: http://en.wikipedia.org/wiki/Software_testing

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 https://trello.com/kdetesting to avoid duplicate work. Please ping Anne-Marie (annma) or Myriam (Mamarok) to be added to the group.

Existing testing infrastructure

Continuous Integration (Jenkins)

KDE already runs a build server with Jenkins: http://build.kde.org/ Please ask the KDE sysadmins if you would like to use it for your project.

Unit tests

UI tests

Code (syntax) tests

A static code analyzing tool is provided by the EnglishBreakfastNetwork.

Existing testing tools


Qt provides a testing module that can be used for unit testing: http://qt-project.org/doc/qt-4.8/qttest.html There also is a possibility to do basic UI testing.

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