>>>>> On Sat, 22 Dec 2007 14:22:05 +0100, [EMAIL PROTECTED] (Andreas J. Koenig)
>>>>> said:
> 1. You get a fail report with an error message that doesn't tell you
> exactly what went wrong.
> 2. You rewrite your test in a way that it does tell you more.
> 3. Release.
> 4. If you now understand the problem, fix it, else goto 1.
Sorry I didn't notice before I posted that this can be refactored into
a while loop:
while (You don't understand the output of your own test script){
Rewrite your test script;
Release;
}
It's as simple as it can get. And I probably do not have to explain
why I'm backing the position of imacat. The developer never tells the
tester what to do. The tester is a device and you can use it IFF you
want to fix your bugs. Otherwise, don't.
There are, of course, rough edges in my point of view. I'm sure we
could do better in many ways. If reporters are intrusive and want to
tell you what to do, they are most probably also wrong. But then there
is a chance to talk or to opt out or to ask for assistance etc.
In case it is not obvious from what I'm saying, let me illustrate:
when I go to work I'm often away from my testing setup for more than
12 hours, sometimes for more than a day. In that time you can easily
get 12 answers from my smoking machine. So before you ever ask *me*,
consider making a developer release just to find out something on my
smoker. It's a bot, after all, just a bit slower.
--
andreas
