maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: Neater way to include/exclude DAO tests?
Date Fri, 23 Nov 2012 09:28:14 GMT
For a more build tool agnostic approach:

Have a test resource that gets the connection details filtered in

Then in your database tests, start each one with a Junit4 Assumption like

assumeThat(credentialsFromTestResource, is(not(nullValue()));

And now you can run all tests from your IDE too

-Stephen

On Monday, 15 September 2008, Dennis Lundberg wrote:

> A totally different way to do it is to run your DAO test cases against
> an embedded database like HSQLDB or perhaps Derby. We use HSQLDB for
> this with at file based database that gets created locally when the
> tests are run.
>
> I know this doesn't answer your question, I'm just thinking outside the
> box here :-)
>
> Haikal Saadh wrote:
> > Hi all.
> >
> > I'm trying to figure out what the best way is to exclude DAO tests. The
> > reason for this being that not everyone who checks a project out may have
> > the credentials necessary to connect to the database.
> >
> > At the moment, I have two profiles like this:
> >
> > <profiles>
> >     <profile>
> >       <id>skip-dao-tests</id>
> >       <activation>
> >         <activeByDefault>true</activeByDefault>
> >       </activation>
> >       <build>
> >         <plugins>
> >           <plugin>
> >             <groupId>org.apache.maven.plugins</groupId>
> >             <artifactId>maven-surefire-plugin</artifactId>
> >             <configuration>
> >               <excludes>
> >                 <exclude>**/WhatEverDaoTest.java</exclude>
> >               </excludes>
> >             </configuration>
> >           </plugin>
> >         </plugins>
> >       </build>
> >     </profile>
> >     <profile>
> >       <id>run-dao-tests</id>
> >       <activation>
> >         <property>
> >           <name>run.dao.tests</name>
> >           <value>true</value>
> >         </property>
> >       </activation>
> >       <build>
> >         <plugins>
> >           <plugin>
> >             <groupId>org.apache.maven.plugins</groupId>
> >             <artifactId>maven-surefire-plugin</artifactId>
> >           </plugin>
> >         </plugins>
> >       </build>
> >       <dependencies>
> >         ...
> >       </dependencies>
> >     </profile>
> > </profiles>
> >
> > This works fine, but it just seems like it's bloating the pom.
> >
> > I could move the DAO tests to a new module, but then, I'd have two
> different
> > sets of cobertura/surefire reports for the same thing.
> >
> > Any different approaches I can try? Or is this pretty much it?
> >
> > Thanks.
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: users-help@maven.apache.org<javascript:;>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message