On Saturday, July 12, 2003, at 08:02 PM, Dave Ford wrote:
The advantage I see is that you get to have test code that has package-level access
Actually, you get that by placing them in the same directory also. So that's
not really an advantage.
and because it's in a separate tree, it's easy to build binaries that don't include all the test code...
Obviously, this is easily accomplished by tools such as Ant or Maven by simply excluding *Test
That assumes that your test code is so simple that everything fits a pattern like that. If so, yes, your are right. But when there's other code that isn't *Test, then it helps to be able to have a separate tree....
Yes, it should be obvious that there are likely to be different files in the test tree - the tests may use mock objects, xml and properties config files and so on. You generally don't want to supply your users with javadoc for your test classes either.
It also makes it much more obvious to someone trying to get to grips with the codebase for the first time what is providing the key functionality and what is just testing it. Division along clear lines of responsibility is generally a good thing (not just for tests).
-- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
