[infinispan-issues] [JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode

Dan Berindei (JIRA) issues at jboss.org
Mon Sep 12 14:18:00 EDT 2016


    [ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292120#comment-13292120 ] 

Dan Berindei edited comment on ISPN-7011 at 9/12/16 2:17 PM:
-------------------------------------------------------------

TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest \(x\)}}.


was (Author: dan.berindei):
TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest (x)}}.

> @AfterClass cleanup doesn't work with @InTransactionMode
> --------------------------------------------------------
>
>                 Key: ISPN-7011
>                 URL: https://issues.jboss.org/browse/ISPN-7011
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Test Suite - Core
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Minor
>              Labels: testsuite_stability
>             Fix For: 9.0.0.Beta1
>
>
> Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
> Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
> {noformat}
> java.lang.IllegalStateException: Two tests with the same name running in parallel: test
> 	at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
> 	at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
> 	at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the infinispan-issues mailing list