Get Involved/Quality: Difference between revisions
m →Communicating with the team: fixed link |
added new chapter |
||
| Line 7: | Line 7: | ||
Early 2012 this team was revived and now has a [https://mail.kde.org/mailman/listinfo/kde-testing mailing list] as well as a channel called #kde-quality on irc.freenode.net. | Early 2012 this team was revived and now has a [https://mail.kde.org/mailman/listinfo/kde-testing 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 | |||
Revision as of 17:00, 5 April 2012
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