[jokosher-devel] The new testing and quality assurance team!
- From: Laszlo Pandy <laszlok2 gmail com>
- To: Jokosher gnome <jokosher-devel-list gnome org>
- Subject: [jokosher-devel] The new testing and quality assurance team!
- Date: Thu, 24 May 2007 20:16:26 -0400
**See the bottom for the time and date of the testing team meeting and
Gstreamer debugging tutorial**
After many bug filled releases I have decided that it is time to put
some processes in to make sure we don't do anything stupid for the grand
1.0 release. To prevent all the bad stuff from slipping through, a new
testing team will be created.
The official title is the "Testing and Quality Assurance Team" and
offers for membership are being extended to *any* member of the
community. All you have to be able to do is run Jokosher and write on
the wiki if it works or not. Obviously we would like you to do more than
that if possible, but no programming skills are required (just testing).
Here are the responsibilities of the testing team:
* Make a large checklist of everything that should be working for the
next release.
* After each beta release go through the checklist and make sure
everything is working.
* Prioritise bugs in the bug tracker. Small bugs that ought to be
fixed get lost because other big important bugs take too long to
implement. Make sure the devs know where the concentrate.
* Constantly harass the developers until the priority bugs are fixed.
This is a perfectly legitimate way for someone on the testing team to
get the bug they hate most fixed.
* Help me (and possibly other devs) implement automated testing.
Basically I need to sort through the large checklist and see which parts
can be easily automated.
Pecisk has been given the position of leader of the testing team, but
anyone else can join. You will need a userdocs.jokosher.org account, and
possibly a wiki account, which you can ask us for on IRC. Also I can add
you to the jokosher-bugs team on launchpad so that you can modify bug
details.
The testing team will have its first meeting to figure out what needs to
be done, and who should do it on Sunday, June 10th at 16:00 UTC.
Following the meeting will be a Gstreamer debugging tutorial so everyone
can get experience tracking down the nasty gstreamer bugs.
Laszlo
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]