We have great tools in KDE to check our code but they are not all used the best they could. We also can go further in testing our software and deliver higher quality releases. This is why we decided to setup a Quality Assurance and Testing Team which will coordinate the efforts for testing better the next release, KDE SC 4.9 and the ones after it.
Here is a link to a document I wrote to expose some ideas in order to have a starting point to debate from: http://www.flootr.com/download.php?file=3374d1db022e34aa39083c22f06abc2e
(the source in .odt is available from my KDE git scratchpad).
The document outlines improvement in using existing tools or following existing policies (marked as "Reinforce") and new testing methods (marked as "New"). For the post 4.9 releases more new targets will be set.
So, what to do to participate? You can subscribe to the mailing list and also join the IRC channel #kde-quality on Freenode and comment on the document or share your experience with testing software or present yourself and tell us you are interested in participating.
We are trying to assess and update the existing wiki resources and update them, this is done on the Community wiki: http://community.kde.org/Getinvolved/Testing. A page for brainstorming also exists if you have practical ideas on how to make this effort work: http://community.kde.org/Getinvolved/Testing/Brainstorming
We will use the beta phase to start testing, in coordination with distributions for providing packages, with the Bug Squad and with developers. Beta testers will be called for before the first beta and meantime we need to have all the documentation ready for them and specific goals set.
Hope you will join!
No comments:
Post a Comment