I am working on a project which basically is converting a java library to C#. While the JCLA did an OK job doing the monkey conversion (all of the boring syntax stuff) of the main code base it really messed up the jUnit tests. While I have been using TDD for a rather long time (started with jUnit now use NUnit) going on 5 years now I never really liked jUnits ideas about TestCases and TestSuites. They always seemed to be more work than they were worth. I like to just write the tests and let the test runner figure out how to report things (with NUnit this is a very natural way of doing things).
So my problem is that all of the java unit test code which has been converted, uses the TestSuite idea in such a way as to actually make it hard to understand what is being tested and the purpose behind the tests is highly obscured. I have actually come to the conclusion that rewriting the tests will take less time and be more coherent in what is trying to be done.
The other thing I really hated about the java code was the fact that all of the test code was intermixed with the main code base. Arrgh this drives me up a wall not only does it cause unnecessary code bloat; it also makes build scripts overly complex and hard to maintain. Causing strange bugs to appear like the fact that the different code bases (main, unit tests, and console app) had a rather nasty circular dependancy (unit test -> main code -> console app -> unit tests). Breaking this gave me a headache. I am going to go take two asprin and I will see you in the morning:)