Having good test coverage of the plugin would be very useful for obvious
reasons. There are currently no tests. The hardest part would be coming up with
a way to test the gui. Need to take a look at how other eclipse plugins achieve
this and follow suit.
The best strategy would probably be to make a few tests to illustrate how it's
done, then add tests for every area of the code that gets touched as a result of
enhancement/bug-fixing/whatever, and hopefullly reach a decent coverage in a bit.
I have started writing extensive junit tests for all the new code that I write
in a new org.eclipse.team.bugzilla.testing plugin/package. I will use this bug
to track what still needs testing, at this point it's everything.
Once I start adding tests to other areas of the code I'll use this as a tracker.
User firstname.lastname@example.org's account has been closed
We are now shipping Mylyn which obsoletes the old bugzilla plugin. Please open
a request at bugs.eclipse.org against Mylyn if this issue persists. Thank you.