Community
Participate
Working Groups
After fixing bug 200419, there is one remaining JUnit failure. I suspect there is another case where we are using the backslash, or some other resource access issue that does not work correctly when deploying the validation plug-in as a jar. The failing test is attached to this defect. Since it occurs in TestSMLModelUnits and not when validating an SML-IF file, it is probably related to the code that assembles SML model units into an SML-IF file. Here is the stack trace: junit.framework.AssertionFailedError: The actual file has less content than expected at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:217) at org.eclipse.cosmos.rm.validation.internal.common.TestUtilities.compareFiles(TestUtilities.java:178) at org.eclipse.cosmos.rm.validation.internal.common.TestUtilities.compareFiles(TestUtilities.java:201) at org.eclipse.cosmos.rm.validation.internal.core.TestSMLModelUnits.validateSMLUnits(TestSMLModelUnits.java:96) at org.eclipse.cosmos.rm.validation.internal.core.TestSMLModelUnits.testRuleInvalidBinding(TestSMLModelUnits.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) 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:120) at org.eclipse.hyades.test.common.junit.HyadesTestCase.run(HyadesTestCase.java:172) at junit.framework.TestSuite.runTest(TestSuite.java:230) at org.eclipse.hyades.test.common.junit.HyadesTestSuite.runTest(HyadesTestSuite.java:457) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.hyades.test.common.junit.HyadesTestSuite.doRun(HyadesTestSuite.java:425) at org.eclipse.hyades.test.common.junit.HyadesTestSuite.run(HyadesTestSuite.java:338) at org.eclipse.hyades.test.common.junit.HyadesTestRunner.run(HyadesTestRunner.java:504) at org.eclipse.hyades.test.java.runner.HyadesJUnitRunner.main(HyadesJUnitRunner.java:207)
Created attachment 76329 [details] test results for failed test
Just to be clear, the conditions for failure are just as in bug 200419, in that this test passes in a development environment, but fails when the validation plug-in is packaged as a jar.
moving target to i8
Ruth, I am moving this to you so that you can reassign as you find appropriate
Still failing in i10 candidate build. It passes when running as a standalone JUnit test, but not as a TPTP test.
*** Bug 216190 has been marked as a duplicate of this bug. ***
Thanks for taking this one, Ali.
Even though I'm targeting this to i12, I'll handle it during the i11 test phase
There were a number of failures under TestSMLModelUnits which I fixed. The test pass now successfully runs in development environment. This should be sufficient for the purpose of the interop. I'm marking this defect fixed.
closing to cleanup bugzilla