Per Mellqvist wrote: > A Java Pro article "Discover Your Inner Classes" by Harris W. Kirk > ( > http://www.fawcette.com/javapro/2002_01/magazine/features/hkirk/default.asp > ) > proposes a simple way of setting up Junit tests that are especially > convenient > when you need many test cases for a certain method.
The drawback of using inner classes is that it is harder to pull out those class files. I also am from the "do not test internal implementation because it is, well, internal", which would be the only real reason for inner classes. I prefer having my unit tests in the same package but in a different directory heirarchy. As far as automatically generating test classes goes, without mental telepathy I'm not sure how much easier it could get. I'm not sure that I'm interested in our very good friends at IntelliJ spending time on this when there are other much higher return capabilities that they could be working on. Like real, complete syntax checking. Like improving memory usage and footprint. Very sincerely, Donald McLean _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
