#24 difference beetwen eclipse and maven test run

[zmicer]

Hi!

When working at https://sourceforge.net/tracker/index.php?func=detail&aid=3052242&group_id=200186&atid=1446552 task I have noticed the following.

I had one test failed when run using maven, it is
testNormalCase(org.jazzteam.jpatterns.patterns.bhv.command.JPCommandImplTest)
Tests run: 101, Failures: 0, Errors: 1, Skipped: 0

Firstly I was thinking this is a new tests and this is a bug inside tests.

But then I tried to run it under eclipse, and it was successful. Then I compared two logs for this tests. See:

A. check attached org.jazzteam.jpatterns.patterns.bhv.command.JPCommandImplTest.txt surefire report which demonstrates exception trace.

[zmicer]

Surefire failed test report

[zmicer]

Please provide here a plan you are going to follow, using steps like:
1) do smth., 1 h.
2) do smth. 1 h
3 do smth. 2 h

Thanks

[zmicer]

Please find trace I have got in eclipse. It is different, then under maven environment, and I can not proceed with understanding what is wrong at initial maven based failed test.

It is seen bug relates to the eclipse classpath - seems to be several data folders are available

java.lang.IllegalStateException: Please be noticed there are mote then one test data folder in the class path. There are [G:\projects\jpatterns\dev\trunk\jpatterns\target\test-classes\testdata, G:\projects\jpatterns\dev\trunk\zmicer.utils\target\test-classes\testdata]
at com.zmicer.utils.junit.ZmicerTestUtils.getFolderWithTestData(ZmicerTestUtils.java:131)
at com.zmicer.utils.junit.ZmicerTestUtils.getFullTestDataFileName(ZmicerTestUtils.java:258)
at org.jazzteam.jpatterns.utils.junit.JPatternsTestUtils.setJVMPropsParams(JPatternsTestUtils.java:164)
at org.jazzteam.jpatterns.patterns.bhv.command.JPCommandImplTest.setUp(JPCommandImplTest.java:58)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)