Testing reports

[Colin Scott]

> Another thing to keep in mind, Colin, is that the developer working 
> on the report might not be the one who breaks it

True, but so what?  *Whoever* broke it, it needs to be fixed.  *Somebody* needs to find out why the report is broken, and until they do nobody will know who broke it (and thus who can fix it!)

> Even worse, but most importantly, the test failure might not be
> noticed right away

Why on earth not?  There seems little point in running a test if you don't bother looking at its output!


Colin