* Karl Dubost wrote:
>I see in WGs often questions about how organizing the testing efforts.
>The first important part being to define who will be in charge of the
>testing efforts. Therefore I have a few questions to ask.
>
>* How do we define the "Test Leader" job?
> - role
> - precise description of tasks
It would make more sense to me to first determine all the work and then
how to manage the work. Also, it would seem that "leaders" rather have
responsibilities than tasks assigned to them, the leader might then let
other people do specific tasks. So it would seem the only task for a
test leader would be to ensure that testing gets done right; but that
does not really help much.
In terms of what would make sense for the QA WG to deliver is a document
listing all the issues around testing like dealing with test
contributions and tracking test issues, what that involves and what
could help to get that done.
Working Groups can then decide themselves whether it makes sense to have
a "Test Leader" and what he would be supposed to do. Unless of course
having a "Test Leader" has been properly researched and clearly
determined as a best practise, but then you would not need to ask the
questions above :-)
--
BjÃ¶rn HÃ¶hrmann Â· mailto:bjoern@hoehrmann.de Â· http://www.bjoernsworld.de
Weinh. Str. 22 Â· Telefon: +49(0)621/4309674 Â· http://bjoern.hoehrmann.de
68309 Mannheim Â· PGP Pub. KeyID: 0xA4357E78 Â· http://www.websitedev.de/