Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > Re: SVN/Junit testing framework best practices

subversion
Discussion topic

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Back to topic list

Re: SVN/Junit testing framework best practices

Author Stephen Connolly <stephen dot alan dot connolly at gmail dot com>
Full name Stephen Connolly <stephen dot alan dot connolly at gmail dot com>
Date 2009-11-01 23:52:51 PST
Message Have a look at Maven and the standard directory layout. (I'm not
suggesting that you change your build process to Maven (although IMHO
that could well be a good thing) but the standard directory layout is
what most projects are moving towards whether they build with Maven or
with something else.

2009/11/2 Jake Stone <jake.the.stone@g​mail.com>:
> 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.ti​gris.org/ds/viewMess​age.do?dsForumId=106​5&dsMessageId=24​13557
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@s​ubversion.tigris.org​].
>

« Previous message in topic | 5 of 6 | Next message in topic »

Messages

Show all messages in topic

Checksum mismatch errors on newly added files Jeremy Aston <jeremy dot aston at realitylogic dot com> Jeremy Aston <jeremy dot aston at realitylogic dot com> 2009-10-28 12:23:31 PDT
     Re: Checksum mismatch errors on newly added files Jeremy Aston <jeremy dot aston at realitylogic dot com> Jeremy Aston <jeremy dot aston at realitylogic dot com> 2009-11-01 09:15:53 PST
         Re: Checksum mismatch errors on newly added files kkolinko Konstantin Kolinko 2009-11-01 10:47:16 PST
             SVN/Junit testing framework best practices Jake Stone <jake dot the dot stone at gmail dot com> Jake Stone <jake dot the dot stone at gmail dot com> 2009-11-01 16:09:36 PST
                 Re: SVN/Junit testing framework best practices Stephen Connolly <stephen dot alan dot connolly at gmail dot com> Stephen Connolly <stephen dot alan dot connolly at gmail dot com> 2009-11-01 23:52:51 PST
                     Re: SVN/Junit testing framework best practices Stephen Connolly <stephen dot alan dot connolly at gmail dot com> Stephen Connolly <stephen dot alan dot connolly at gmail dot com> 2009-11-01 23:54:29 PST
Messages per page: