SVN/Junit testing framework best practices

Hello all,

I am working on a few small Java projects, and we are trying to switch
to test-driven development in the near future. We have a relatively
standard branches/dist/tags/trunk layout, inside of trunk is just the
java package folders ("com/website/project..."). I was wondering how
project managers tend to handle the organization of unit testing code.

A few ideas occurred to us:
1) Just have a "test" folder in each project, which replicates the
project directory (ugly). Store any unit tests for the project there,
and simply exclude that folder when creating a JAR or other distribution.

This one is easy to work with, but a little ugly when working with the
unit tests.

2) Change the repository to have "src" and "tests" folder, organized
with the same java packaging layout. Each category goes in it's own
folder; to run tests, you checkout your projects "src" and "tests."

I'd think this makes it too complicated to run tests on a project, and
therefore they wouldn't get run often enough.

I also someday want to set up a Hudson continuous integration server
("https://hudson.dev.java.net/"), so I'd want to keep that in mind as well.
A few Google searches haven't turned up anything interesting, what are
your thoughts?

Thanks for your help!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2413557

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-02 01:10:25 CET