[ https://issues.jboss.org/browse/ARQ-127?page=com.atlassian.jira.plugin.sy... ] Michal Vanco commented on ARQ-127: ---------------------------------- Hi Aslak (and others), today I came back to this issue after some time as it's still seems to be a critical thing which we would appreciate with arquillian-testng-stangalone library. I still used the same example just with updated dependencies. I tried some hacking at Arquillian.class and it seems like the usage of ThreadLocal is breaking this TestNG parallelism feature... {noformat} ... Running TestSuite BEFORE SUITE, runner:null Going to set test runner:org.jboss.arquillian.test.impl.EventTestRunnerAdaptor@266c6ce1, threadLocal:java.lang.ThreadLocal@18603b7c BEFORE CLASS, runner:null BEFORE CLASS, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER TEST, runner:null AFTER CLASS, runner:null AFTER CLASS, runner:null AFTER SUITE, runner:org.jboss.arquillian.test.impl.EventTestRunnerAdaptor@266c6ce1 {noformat} It's initialized once at the suite level, but none of the class/test methods are able to access it and it ends up with same message: {noformat} java.lang.IllegalStateException: No TestRunnerAdaptor found, @BeforeSuite has not been called at org.jboss.arquillian.testng.Arquillian.verifyTestRunnerAdaptorHasBeenSet(Arquillian.java:252) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:104) {noformat} [~aslak] - can you please confirm that there is any chance that Arquillian will be sometime able to handle this kind of parallelism (at least on class level)? Or maybe there is some quick hint you can provide... or should I just forget this requirement or workaround it at "ugly way"? Thanks a lot for your help! And I also thanks [~lfryc] for his help and support :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)