20 Oct
2006
20 Oct
'06
5:10 p.m.
I understand that many testers are not coders, but having at least one or two
coders on each testing team with the non-coder testers would make the teams
self sufficient and be able to fix bugs more rapidly.
On Friday 20 October 2006 02:35, Toby Smithe wrote:
On Fri, 2006-10-20 at 08:11 +0100, Murphy, Ged
(Bolton) wrote:
I hate ugly text formatting ...
Resending in a (hopefully) readable format.
Jerry wrote:
Yeah. I don't code, but I like to help out testing (and will start again
once I fixed my partition layout...). If I could code, that's what I
would be doing; as it is, though, I cannot fix these bugs.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev After a team says that it has fixed the bug ...
<snip>
Each team may have mentees associated with it.
The teams would then
help and guide their mentees in testing and coding, and these mentees
will help with the work load that the regular testers have. The goal
here is to guide the mentees to be regular developers and either stay
in testing or move on to other parts of the project and have.
I'm a little confused with the idea of the testing teams fixing bugs.
Testers aren't usually coders. It's great if they are as they can fix the
bugs they find, but in general testing positions are filled by people who
want to help the project, but aren't programmers.
If a tester is a programmer too, I think you'll find that do a lot more
programming than testing, as shown by our tree instability at the moment
;)