ansaurus

Question

Different JUnit-result starting from Eclipse vs. mvn test

Answer 1

A:

What I've noticed that sometimes my unit test outputs change depending on the level of sandboxing done by the used testing tool. For example Eclipse seems to sandbox current selection(class, package, project) to a single setup-test-teardown cycle in same context while our CI seems to sandox every single unit test as setup-test-teardown cycle.

What this means is that if your test1 has a side effect which is then used in test2, it may work in Eclipse but it also may fail elsewhere. If this is the case, you need to rewrite your unit tests at least partly to decouple them from each other.

Esko 2009-10-01 07:45:06

Thanks a lot for your answer...I thought about something like that; but if I run only that specific method out of Eclipse, it doesn't work either...

swalkner 2009-10-01 07:59:43

Answer 2

A:

My remarks/question:

when you remove line "hibernate.hbm2ddl.auto" - the default action is none
what base test class you use? Try extends class org.springframework.test.jpa.AbstractJpaTests - it does rollback after each method
from exception stack trace seems to tables aren't clean before inserts
where your database (file) is stored? Maybe maven build clean database file.
do you use any maven plugins that are run in maven and not in eclipse (like hibernate3-maven-plugin)?

EDIT: In my opinion test should be run in clean database and leave database clean, so each test/method should rollback after execution. Look at my qestion and responses. I think that using hibernate3-maven-plugin is optional.

cetnar 2009-10-01 08:09:47

- my Test class extends AbstractTransactionalJUnit4SpringContextTests- database file is stored locally; maven clean didn't help...- most interesting: yes, hibernate3-maven is used!

swalkner 2009-10-01 08:20:58

Answer 3

+2 A:

Based on the SQLIntegrityConstraintViolationException it looks like your delete statements are not being executed, do you perhaps have two delete.sql files or not have src/test/resources configured as a source location in Eclipse?

The applicationContext.getResource("delete.sql") call will expect to find delete.sql in the output directory. In a Maven build the contents of src/test/resources will be copied to target/test-classes, this will only be done in an Eclipse build if the source location is defined.

The true at the end of the first executeSqlScript call means the process will continue without throwing an exception in the event of an error, so it may be that the resource is not found, and the delete statements not executed. If you run the build with the option set to false (and existing content) does it fail?

Note you can configure the Eclipse .classpath file to output test content to target/test-classes to avoid conflicts.

The steps to do this are:

Open the project properties (alt-enter)
Select**Java Build Path**
Select the Source tab
Click on Allow output folders for source folders. This adds a new entry to the source folder tree.
Expand the source folder tree.
Double-click on the Output folder: entry.
A dialog asks you if you want to use the project's default output folder or a specific output folder. Choose the second option and click Browse...
Select the folder you want and click OK and then Finish.

You should end up with the following entries in the .classpath file:

<classpathentry kind="src" output="target/test-classes" path="src/test/java"/>
<classpathentry kind="src" output="target/test-classes" path="src/test/resources"/>

Rich Seller 2009-10-01 08:20:17

Thanks a lot for that information!I checked - there's only one delete.sql-file and while debugging it becomes clear that it's really found.

swalkner 2009-10-01 08:28:26

Dude! Thanks very much for this!

Sergio Oliveira Jr. 2010-07-19 00:16:05

ansaurus

tags:

views:

answers:

Different JUnit-result starting from Eclipse vs. mvn test

related questions