[Foxtrot] Thought on bug reporting

[Alan Lawrence]

I reckon some scripts to set up all the environment variables etc. for RMI
would be helpful....anyone?

--Alan

On Wed, 14 Feb 2001, Michael Pinna wrote:

> Me again.
> 
> Something we probably ought to think about when reporting bugs:
> 
> >From the programmer's point of view, it would be really nice to be told
> not only what the incorrect behaviour of the given class is, but also
> how to reproduce it on the level of - run this test harness with these
> arguments, or whatever. That way, I can guarantee being able to
> reproduce it easily, etc etc.
> 
> I have a feeling the problem stems from the fact that I don't understand
> enough of the client/server architecture even to run the application :)
> but in a sense I shouldn't really need to, in order to fix bugs in my
> algorithmy code.
> 
> Does that sound reasonable? At least in the sense that it would save a
> lot of time for me if a tester told me exactly how a bug was found.
> 
> Comments welcome...
> 
> Mike
> 
> -- 
> "...like the nasty robot holding a dancing building."
>       --Anon
> 
> 
> 
> _______________________________________________
> Foxtrot mailing list
> Foxtrot@srcf.ucam.org
> http://www.srcf.ucam.org/mailman/listinfo/foxtrot
>