MDR Issuezilla, testing, and verifying issues

Hi,

I happened to notice that I have reported a number of issues against the 
MDR module (38) but I haven't done a good job of marking them "verified" 
after they were resolved. I have looked over all the issues that I have 
reported that are marked RESOLVED, and as far as I'm concerned they were 
all resolved satisfactorily with the exception of the one below. I don't 
know if you want me to go back and mark these all as VERIFIED or not, or 
what the criteria is for marking something VERIFIED.

The one that is RESOLVED/FIXED that I am not sure about is:

28937 XmiReader.read returns all objects, not just outermost objec...

As Martin mentioned in the bug, my understanding about the result of 
XmiReader.read() was wrong. Once Martin corrected my misunderstanding I 
realized that the result of XmiReader.read() is useless to my 
application (to everybody?!?) so I've since changed my code to ignore 
the return value. Since I can't really have a use for the fix, and I 
don't understand the XMIReader code well enough to verify it by 
inspection, and I don't have time to write unit tests, somebody else 
will have to verify it. In particular, somebody might verify that it 
returns the correct result when the XMI diff mechanism is used, as well 
as any other cases where inter-document links are used (I'm not even 
sure what the correct result is in these cases).

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. 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.

- Brian