May 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-77) Support @EJB injection

by Andrew Lee Rubinger (JIRA)

Support @EJB injection ----------------------- Key: ARQ-77 URL: https://jira.jboss.org/jira/browse/ARQ-77 Project: Arquillian Issue Type: Feature Request Components: OpenEJB Containers Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name). Note that portable JNDI is under java:global, so only accessible to local JVMs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
16
0 / 0

[JBoss JIRA] Created: (ARQAJO-45) Provide automatic escapes for JQuery/other locator strategy dangerous characters

by Karel Piwko (JIRA)

Provide automatic escapes for JQuery/other locator strategy dangerous characters -------------------------------------------------------------------------------- Key: ARQAJO-45 URL: https://issues.jboss.org/browse/ARQAJO-45 Project: Arquillian Ajocado Issue Type: Enhancement Affects Versions: 1.0.0.Alpha2 Reporter: Karel Piwko Assignee: Lukas Fryc Fix For: 1.0.0.Alpha3 Selenium command processor behaves differently on different Selenium version. Consolidate the behavior and provide automatic escapes for dangerous characters according to the locator strategy. Implementation note: SimplifiedFormatter couldn't be used to do this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-197) Research support for @Deployment on multiple levels

by Aslak Knutsen (JIRA)

Research support for @Deployment on multiple levels --------------------------------------------------- Key: ARQ-197 URL: https://jira.jboss.org/browse/ARQ-197 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Priority: Minor One deployment pr TestCase might not always be the ideal solution. Research how we can deploy multiple TestCases with one Deployment and test them all at once. -- 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

12 years, 1 month

7
15
0 / 0

[JBoss JIRA] Created: (ARQ-299) Create a IN_CONTAINER Exception Proxy

by Aslak Knutsen (JIRA)

Create a IN_CONTAINER Exception Proxy ------------------------------------- Key: ARQ-299 URL: https://jira.jboss.org/browse/ARQ-299 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen On Exception, the IN_CONTAINER TestRunner tries to serialize the caught Exception back to the Client so it can be displayed as if it was local. The problem is if you don't have the Client lib on Client Classpath or you have the wrong version of it. This results in a Deserialization exception on the Client. We probably have to not Serialize the actual Exception, but serialize a Textual representation of it, which we can create a 'proxy' Exception of on the client side and make it 'look' like the original. -- 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

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (ARQAJO-62) Create Seam Forge plugin for Ajocado

by Lukáš Fryč (JIRA)

Create Seam Forge plugin for Ajocado ------------------------------------ Key: ARQAJO-62 URL: https://issues.jboss.org/browse/ARQAJO-62 Project: Arquillian Ajocado Issue Type: Task Components: integration 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

12 years, 1 month

2
15
0 / 0

[JBoss JIRA] Created: (ARQAJO-23) Setup matrix jobs for browser support

by Lukas Fryc (JIRA)

Setup matrix jobs for browser support ------------------------------------- Key: ARQAJO-23 URL: https://issues.jboss.org/browse/ARQAJO-23 Project: Arquillian Ajocado Issue Type: Feature Request Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 1.0.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
21
0 / 0

[JBoss JIRA] Created: (ARQAJO-67) Reduce logging levels

by Karel Piwko (JIRA)

Reduce logging levels --------------------- Key: ARQAJO-67 URL: https://issues.jboss.org/browse/ARQAJO-67 Project: Arquillian Ajocado Issue Type: Feature Request Components: junit, testng Affects Versions: 1.0.0.Alpha2 Reporter: Karel Piwko Assignee: Lukáš Fryč Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine. It makes execution of the test slower and this information is not required until debugging. It manifest namely with JUnit which redirects test output to console. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (ARQAJO-36) Introduce annotation to control lifecycle of selenium session

by Lukas Fryc (JIRA)

Introduce annotation to control lifecycle of selenium session ------------------------------------------------------------- Key: ARQAJO-36 URL: https://issues.jboss.org/browse/ARQAJO-36 Project: Arquillian Ajocado Issue Type: Feature Request Reporter: Lukas Fryc Assignee: Lukas Fryc Following options are being considered: BEFORE_SUITE BEFORE_CLASS BEFORE_METHOD -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
9
0 / 0

[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

12 years, 3 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

12 years, 3 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2011