September 2012 - arquillian-issues

[JBoss JIRA] (ARQ-1103) Event is logged even though it is not executed because observer got unresolvable arguments

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQ-1103: ------------------------------- Summary: Event is logged even though it is not executed because observer got unresolvable arguments Key: ARQ-1103 URL: https://issues.jboss.org/browse/ARQ-1103 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.2.Final Reporter: Lukáš Fryč Priority: Minor {{EventContextImpl}} fires logs event processing and then invokes observer method: https://github.com/arquillian/arquillian-core/blob/1.0.2.Final/core/impl-... but {{ObserverImpl}} does not invoke an observer method if it contains unresolvable argument: https://github.com/arquillian/arquillian-core/blob/1.0.2.Final/core/impl-... ---- We should indicate that given observer method does have unresolved argument instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-192) Support enriching also List<WebElement> fields annotated with @FindBy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-192?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-192: ------------------------------ Priority: Critical (was: Major) > Support enriching also List<WebElement> fields annotated with @FindBy > --------------------------------------------------------------------- > > Key: ARQGRA-192 > URL: https://issues.jboss.org/browse/ARQGRA-192 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Critical > Fix For: 2.0.0.Alpha3 > > > Currently there is only supported initialization of: > {code} > @FindBy(strategy=locator) > WebElement element; > {code} > Add also support for this use case: > {code} > @FindBy(strategy=locator) > List<WebElement> elements; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-192) Support enriching also List<WebElement> fields annotated with @FindBy

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-192?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-192: ------------------------------ Fix Version/s: 2.0.0.Alpha3 > Support enriching also List<WebElement> fields annotated with @FindBy > --------------------------------------------------------------------- > > Key: ARQGRA-192 > URL: https://issues.jboss.org/browse/ARQGRA-192 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 2.0.0.Alpha3 > > > Currently there is only supported initialization of: > {code} > @FindBy(strategy=locator) > WebElement element; > {code} > Add also support for this use case: > {code} > @FindBy(strategy=locator) > List<WebElement> elements; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
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] (ARQGRA-192) Support enriching also List<WebElement> fields annotated with @FindBy

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-192?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-192: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/44 > Support enriching also List<WebElement> fields annotated with @FindBy > --------------------------------------------------------------------- > > Key: ARQGRA-192 > URL: https://issues.jboss.org/browse/ARQGRA-192 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Juraj Húska > > Currently there is only supported initialization of: > {code} > @FindBy(strategy=locator) > WebElement element; > {code} > Add also support for this use case: > {code} > @FindBy(strategy=locator) > List<WebElement> elements; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-872) Integration tests are failing with Glassfish 3.1.2 embedded

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-872: ---------------------------------- Summary: Integration tests are failing with Glassfish 3.1.2 embedded Key: ARQ-872 URL: https://issues.jboss.org/browse/ARQ-872 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha4 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

12 years, 3 months

1
4
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

12 years, 3 months

1
7
0 / 0

[JBoss JIRA] (ARQ-1017) Update APE to Core 1.0.1.Final

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1017: ----------------------------------- Summary: Update APE to Core 1.0.1.Final Key: ARQ-1017 URL: https://issues.jboss.org/browse/ARQ-1017 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Bartosz Majsak -- 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

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] (ARQ-1099) Add arquillian.xml configuration section to the documentation

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created ARQ-1099: -------------------------------------- Summary: Add arquillian.xml configuration section to the documentation Key: ARQ-1099 URL: https://issues.jboss.org/browse/ARQ-1099 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Hardy Ferentschik At the moment there is no chapter in the documentation which describes the different workings of arquillian.xml. AFAIU each container adapter can have its own properties, but I think there is still a need to describe the basic workings, eg how to select a named container configuration via arquillian.launch. See also: * http://stackoverflow.com/questions/9740938/how-to-select-a-container-by-q... * http://stackoverflow.com/questions/10119544/where-can-i-find-the-arquilli... Given that arquillian.xml is the main configuration file it is only reasonable that people try to understand Arquillian from this angle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-186) Rename Component Objects dependencies to Page Fragments

by Juraj Húska (JIRA)

Juraj Húska created ARQGRA-186: ---------------------------------- Summary: Rename Component Objects dependencies to Page Fragments Key: ARQGRA-186 URL: https://issues.jboss.org/browse/ARQGRA-186 Project: Arquillian Graphene Issue Type: Task Components: api, core, spi Affects Versions: 2.0.0.Alpha1 Reporter: Juraj Húska Assignee: Juraj Húska Concept of Component Objects were renamed to *Page Fragments*. See [this|https://community.jboss.org/thread/204730?tstart=0] discussion for more reference. Rename all affected dependencies in Graphene code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2012