Dear group,
I would like to ask whether someone knows the work around for the error by
advising test class being executed via JUnit test suite.
With crosscutting the invocation of method in JUnit test class, I encounter
the following types of exception for running test via JUnit test suite
(using @SuiteClasses annotation):
VerifyError with CTW:
- java.lang.VerifyError: Expecting a stackmap frame at branch target 501
in method
com.newmainsoftech.jecommerce.dao.impl.AbstractCategoryFacadeImplTest.test_create_via_cascade()V
at offset 3
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2451)
at java.lang.Class.getMethod0(Class.java:2694)
at java.lang.Class.getMethod(Class.java:1622)
at
org.junit.internal.builders.SuiteMethodBuilder.hasSuiteMethod(SuiteMethodBuilder.java:18)
at
org.junit.internal.builders.SuiteMethodBuilder.runnerForClass(SuiteMethodBuilder.java:10)
- java.lang.VerifyError: (class:
com/newmainsoftech/jecommerce/dao/impl/AbstractCategoryFacadeImplTest,
method: test_create signature: ()V) Unable to pop operand off an empty stack
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2451)
at java.lang.Class.getMethod0(Class.java:2694)
at java.lang.Class.getMethod(Class.java:1622)
at
org.junit.internal.builders.SuiteMethodBuilder.hasSuiteMethod(SuiteMethodBuilder.java:18)
at
org.junit.internal.builders.SuiteMethodBuilder.runnerForClass(SuiteMethodBuilder.java:10)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
NoSuchMethodError with LTW:
test_create(com.newmainsoftech.jecommerce.dao.impl.AbstractCategoryFacadeImplTest)
Time elapsed: 0.156 sec <<< ERROR!
java.lang.NoSuchMethodError:
com.newmainsoftech.jecommerce.dao.TestCentral$DumpTestExceptionAspect.aspectOf()Lcom/newmainsoftech/jecommerce/dao/TestCentral$DumpTestExceptionAspect;
at
com.newmainsoftech.jecommerce.dao.impl.AbstractCategoryFacadeImplTest.test_create(AbstractCategoryFacadeImplTest.java:137)
The above such exceptions are not hit when the same unit test is executed
individually not via test suite.
I would like to know of the way of working around such errors even test is
executed via test suite.
Regards,
Art
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
