February 2012 - arquillian-issues

[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] (ARQ-763) Create TestNG tests covering most important use cases.

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-763: ---------------------------------- Summary: Create TestNG tests covering most important use cases. Key: ARQ-763 URL: https://issues.jboss.org/browse/ARQ-763 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
7
0 / 0

[JBoss JIRA] Created: (ARQ-579) We need to be able to override default protocol on a container level

by José Freitas (JIRA)

We need to be able to override default protocol on a container level -------------------------------------------------------------------- Key: ARQ-579 URL: https://issues.jboss.org/browse/ARQ-579 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: José Freitas Using <defaultProtocol type="Servlet 3.0" /> makes it impossible to run tests on tomcat-embedded-6. We need to be able to override default protocol on a container level, so we can use defaultProtocol property and still share an arquillian.xml between older servers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
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] (ARQAJO-116) Support XHR Halter

by Lukáš Fryč (Created) (JIRA)

Support XHR Halter ------------------ Key: ARQAJO-116 URL: https://issues.jboss.org/browse/ARQAJO-116 Project: Arquillian Ajocado Issue Type: Sub-task Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
14
0 / 0

[JBoss JIRA] (ARQAJO-117) Support for Websocket Halter

by Lukáš Fryč (Created) (JIRA)

Support for Websocket Halter ---------------------------- Key: ARQAJO-117 URL: https://issues.jboss.org/browse/ARQAJO-117 Project: Arquillian Ajocado Issue Type: Sub-task Affects Versions: 2.0-Tracking Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
2
0 / 0

[JBoss JIRA] (ARQAJO-115) Support for HTTP Halter

by Lukáš Fryč (Created) (JIRA)

Support for HTTP Halter ----------------------- Key: ARQAJO-115 URL: https://issues.jboss.org/browse/ARQAJO-115 Project: Arquillian Ajocado Issue Type: Sub-task Affects Versions: 2.0-Tracking Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
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: (ARQAJO-95) Adopt Ajocado for usage of WebDriver/Selenium 2 API

by Lukáš Fryč (JIRA)

Adopt Ajocado for usage of WebDriver/Selenium 2 API --------------------------------------------------- Key: ARQAJO-95 URL: https://issues.jboss.org/browse/ARQAJO-95 Project: Arquillian Ajocado Issue Type: Feature Request Reporter: Lukáš Fryč Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
11
0 / 0

[JBoss JIRA] (ARQAJO-108) Adopt retrievers API to Selenium 2

by Lukáš Fryč (Created) (JIRA)

Adopt retrievers API to Selenium 2 ---------------------------------- Key: ARQAJO-108 URL: https://issues.jboss.org/browse/ARQAJO-108 Project: Arquillian Ajocado Issue Type: Feature Request Components: api, core Reporter: Lukáš Fryč Fix For: 2.0-Tracking -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012