Re: MDR Issuezilla, testing, and verifying issues

Hi Brian,
I don't mind if the issue that is marked resolved is not marked 
VERIFIED. Once I mark an issue resolved fixed, it is closed for me/us. 
We are not marking bugs as RESOLVED if we are not sure that they are 
really resolved. But still the fix may not satisfy the reporter. In that 
case, the reporter or anyone else is welcome to reopen the issue to 
bring it back to our attention.

 > Regarding unit tests, I can start writing my test cases for bug reports
 > as JUnit test cases if you think that would be helpful (presumably, to
 > use as regression tests). I think I understand your test framework well
 > enough to write something that will work with it.

Don't bother with it for bugs that can be easily reproduced by us. But 
this would be very helpful for bugs that are not reproducible by a code 
that is part of MDR modules. (so that we would need to write a specific 
test case in order to reproduce it anyway)

 > I think that if you
 > wrote up a very specific document ("subclass MDRTestCase, override XXX,
 > do YYY...") then you might be able to convince more people to submit a
 > JUnit test along with the report.

I agree. We would of course welcome any draft of such document :) (but 
don't bother if you don't have time).
Thanks,
Martin