July 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-245) When using TestNG, an embedded container (e.g. weld-ee) and multiple test classes, test fail randomly

by Adam Warski (JIRA)

When using TestNG, an embedded container (e.g. weld-ee) and multiple test classes, test fail randomly ----------------------------------------------------------------------------------------------------- Key: ARQ-245 URL: https://jira.jboss.org/browse/ARQ-245 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Affects Versions: 1.0.0.Alpha3 Reporter: Adam Warski As TestNG interleaves tests from different classes (even in single-threaded mode), cleanup of one class (@AfterClass) can happen to be invoked in the middle of executing tests from another class. More precisely, it clears the Container instance: at org.jboss.weld.Container.cleanup(Container.java:108) at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:460) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockServletLifecycle.endApplication(MockServletLifecycle.java:126) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.stopContainer(TestContainer.java:139) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.undeploy(WeldEEMockContainer.java:131) at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:61) at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:47) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:86) at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:90) at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:227) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:124) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) (notice the AfterClass, Arquillian:83), which causes any subsequent test to throw: org.jboss.arquillian.impl.event.FiredEventException: java.lang.IllegalStateException: Singleton is not set at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:113) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:97) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeMethod(Invoker.java:494) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) Caused by: java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:58) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:138) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:100) at org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) at org.jboss.weld.servlet.HttpSessionManager_$$_javassist_14.setSession(HttpSessionManager_$$_javassist_14.java) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer$1.callback(WeldEEMockContainer.java:111) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer$1.callback(WeldEEMockContainer.java:95) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 28 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-368) Support IN_CONTAINER mode with Selenium Extension

by Karel Piwko (JIRA)

Support IN_CONTAINER mode with Selenium Extension ------------------------------------------------- Key: ARQ-368 URL: https://issues.jboss.org/browse/ARQ-368 Project: Arquillian Issue Type: Feature Request Components: Extension - Selenium Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Probably the biggest advantage of having a Selenium Test running within CONTAINER is ability to easily mockify internals used within test case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (ARQAJO-40) Enable handling of multiple AjaxSelenium instances in one class

by Lukas Fryc (JIRA)

Enable handling of multiple AjaxSelenium instances in one class --------------------------------------------------------------- Key: ARQAJO-40 URL: https://issues.jboss.org/browse/ARQAJO-40 Project: Arquillian Ajocado Issue Type: Feature Request Reporter: Lukas Fryc Assignee: Lukas Fryc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (ARQ-376) Environment configuration is overridden by arquillian.xml

by Karel Piwko (JIRA)

Environment configuration is overridden by arquillian.xml --------------------------------------------------------- Key: ARQ-376 URL: https://issues.jboss.org/browse/ARQ-376 Project: Arquillian Issue Type: Bug Components: Configuration, JBoss Containers Affects Versions: 1.0.0.Beta1 Reporter: Karel Piwko Priority: Blocker It is not possible to define JAVA_HOME and JBOSS_HOME for managed containers via system properties because these values are used only during configuration creation and they will be overridden by arquillian.xml value. This is not desired behaviour how to make test execution flexible enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (ARQ-518) Support @PersistenceContet injection in weld-ee mock container

by Michal Huniewicz (JIRA)

Support @PersistenceContet injection in weld-ee mock container -------------------------------------------------------------- Key: ARQ-518 URL: https://issues.jboss.org/browse/ARQ-518 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Weld Containers Reporter: Michal Huniewicz I'd like weld-ee container to inject @PersistenceContext. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-219) Implement an embedded Spring container

by Dan Allen (JIRA)

Implement an embedded Spring container -------------------------------------- Key: ARQ-219 URL: https://jira.jboss.org/browse/ARQ-219 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen Implement an embedded container that bootstraps the Spring bean container and provides injection of Spring beans into the test class. This container will require classpath trickery (perhaps the ShrinkWrap classloader) to narrow the visibility of the scanner to classes in the test archive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (ARQ-293) Support container targeted deployments

by Aslak Knutsen (JIRA)

Support container targeted deployments -------------------------------------- Key: ARQ-293 URL: https://jira.jboss.org/browse/ARQ-293 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Fix For: 1.0.0.CR1 in some cases it is useful to be able to define different @Deployments pr target container. e.g. Container X needs a different defined deployment descriptor to work etc.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (ARQ-355) Support fluent API and @DeploymentTarget for Rules

by Aslak Knutsen (JIRA)

Support fluent API and @DeploymentTarget for Rules -------------------------------------------------- Key: ARQ-355 URL: https://issues.jboss.org/browse/ARQ-355 Project: Arquillian Issue Type: Feature Request Components: Extension - Byteman Reporter: Aslak Knutsen Priority: Minor With multi container support in arquillian, the byteman integration should support @DeploymentTarget for specifying which container a rule should be deployed on. Byteman integration could follow the ShrinkWrap fluent API and make a API for rule creation, instead of having it only declarative via Annotaitons. @BMRule @DeploymentTarget("name") public static Rule createExceptionRule() { return Byteman.rule()..... } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQAJO-63) Screencast on Ajocado

by Lukáš Fryč (JIRA)

Screencast on Ajocado --------------------- Key: ARQAJO-63 URL: https://issues.jboss.org/browse/ARQAJO-63 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-64) Blog on Ajocado

by Lukáš Fryč (JIRA)

Blog on Ajocado --------------- Key: ARQAJO-64 URL: https://issues.jboss.org/browse/ARQAJO-64 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2011