and putting the integration tests into something like "src/itests" is
OK
for me.
Much better than putting them into "src/test" or "tests" (at root
level)
-M
On Tue, May 21, 2013 at 5:30 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Tue, May 21, 2013 at 5:19 PM, Douglas Campos <qmx(a)qmx.me> wrote:
> On Tue, May 21, 2013 at 01:50:19PM +0200, Matthias Wessendorf wrote:
> > On Tue, May 21, 2013 at 1:38 PM, Kris Borchers <kris(a)redhat.com> wrote:
> > > To me, the src directory is for just that, source, and should never be
> > > cluttered with tests.
> At least in Java lands, the tests are written using source code :P
>
> > in maven, it's default that SOURCE code goes to
"src/main/$LANGUAGE";
> tests
> > (unit tests) go to "src/test/$LANGUAGE"
> Have y'all considered using maven-failsafe-plugin[1]? In this case, the
> integration tests only run when you invoke mvn verify (and a name
> pattern can be specified for the integration tests)
>
> [
1]:http://maven.apache.org/surefire/maven-failsafe-plugin/index.html
Used before - not sure, but I do not like mixing unit and integration
tests, in one maven project :)
>
>
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf