Infinitest to have a continuous feedback loop from my unit tests while developing. Recently I noticed that when I’m working with m2e some of my testcases were red when Inifitest executed them, but were green when I run the Junit tests via Eclipse. After thinking about it, I figured out that all tests that were using configuration or input files from my src/test/resources folder were failing.

"> Infinitest to have a continuous feedback loop from my unit tests while developing. Recently I noticed that when I’m working with m2e some of my testcases were red when Inifitest executed them, but were green when I run the Junit tests via Eclipse. After thinking about it, I figured out that all tests that were using configuration or input files from my src/test/resources folder were failing.

"> Infinitest to have a continuous feedback loop from my unit tests while developing. Recently I noticed that when I’m working with m2e some of my testcases were red when Inifitest executed them, but were green when I run the Junit tests via Eclipse. After thinking about it, I figured out that all tests that were using configuration or input files from my src/test/resources folder were failing.

" />
KOPIS.DE

Auf diesen Seiten findest Du die Projekte und Blogposts von Carsten Ringe.

Using Infinitest with m2e in Eclipse

13 February 2014

I’m a huge fan of Infinitest to have a continuous feedback loop from my unit tests while developing. Recently I noticed that when I’m working with m2e some of my testcases were red when Inifitest executed them, but were green when I run the Junit tests via Eclipse. After thinking about it, I figured out that all tests that were using configuration or input files from my src/test/resources folder were failing.

Looks like Eclipse (or rather, m2e) is using a different classpath order than Infinitest.

Solution is to put the folder src/test/resources to the top of the classpath via the project settings. That way the test resources are loaded before resources from src/main/resources. :smile: