maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Haikal Saadh <spam.hai...@gmail.com>
Subject Re: Neater way to include/exclude DAO tests?
Date Mon, 15 Sep 2008 09:00:55 GMT

Yeah, that's how I started out initially, but unfortunately, this app's a
wrapper for an Oracle database, and thus, needs oracle specific SQL.


Dennis Lundberg-2 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
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Neater-way-to-include-exclude-DAO-tests--tp19485851p19489322.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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


Mime
View raw message