|
|
| (67 intermediate revisions by 9 users not shown) |
| Line 1: |
Line 1: |
| __NOTOC__
| | #REDIRECT [[Quality_Assurance]] |
| == Becoming a KDE Tester ==
| |
| | |
| [[Image:testing.png|Testing|left]]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 [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
| |
| | |
| == Initial steps ==
| |
| | |
| Since this is a new start we need to define the exact goal of this team. There is a [http://community.kde.org/Getinvolved/testing/Brainstorming 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 ==
| |
| | |
| === 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.
| |
