Acceptance tests best practice

["J. Matthew Pryor" <jm...@yahoo.com>]

I am wondering if anyone can spare a few thoughts on how best to handle
acceptance tests with maven.

I love & use the JUnit support for unit tests, and grok the way they Unit
tests are always run before jar.

Acceptance tests on the other hand would want o be used in such a tightly
iterative (TDD?) sort of way.

I have taken a tiny peek at SelfEsteem
(http://opensource.thoughtworks.com/projects/selfesteem.html), and would
expect to use Junit to drive the acceptance tests, but I am not sure exactly
where to place them in my project and how to handle them from the POM point
of view or from an execution point of view.

Source code wise, I was thinking of placing them in
${basedir}/src/acceptancetest/java, but then I have the problem of how to
get them compiled and I am loathe to deal with the 'multiple source
directory' trout.

Then maybe I thought put them in a top-level package and try & get them
excluded from the jar?

Maybe a separate sub-project & use multisite?

Anyway if anyone can share some experience I love to hear it

Matthew


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org