October 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-284) Configuration options should be loadable from multiple sources

by Aslak Knutsen (JIRA)

Configuration options should be loadable from multiple sources -------------------------------------------------------------- Key: ARQ-284 URL: https://jira.jboss.org/browse/ARQ-284 Project: Arquillian Issue Type: Feature Request Components: Configuration Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 The configuration should be able to get configuration from multiple locations and override in some order.. system properties, properties file, maven config, arquillian.xml 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

12 years, 6 months

5
6
0 / 0

[JBoss JIRA] Created: (ARQ-526) Support OpenWebBeans 1.1 Container

by Aslak Knutsen (JIRA)

Support OpenWebBeans 1.1 Container ---------------------------------- Key: ARQ-526 URL: https://issues.jboss.org/browse/ARQ-526 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenWebBeans Containers Affects Versions: openwebbeans_1.0.0.CR1 Reporter: Aslak Knutsen Fix For: openwebbeans_1.0.0.Final API in OpenWebBeans has changed, addBeansXMLLocation has changed from URL to String. Evaluate if we should use the OpenWebBeans SPIs instead of the extending AbstractMetaDataDiscovery https://github.com/arquillian/arquillian-container-openwebbeans/blob/mast... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (ARQ-403) OpenWebBeans container should support WebArchive deployments

by Aslak Knutsen (JIRA)

OpenWebBeans container should support WebArchive deployments ------------------------------------------------------------ Key: ARQ-403 URL: https://issues.jboss.org/browse/ARQ-403 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenWebBeans Containers Affects Versions: 1.0.0.Alpha5 Reporter: Aslak Knutsen Priority: Minor Fix For: 1.0.0.Beta1 OpenWebBeans integration only look for META-INF/beans.xml, should also look for WEB-INF/beans.xml. And be able to load Bean definitions from WEB-INF/classes, and setup the Resource locations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (ARQ-444) MethodContext is not correctly free'd

by Karel Piwko (JIRA)

MethodContext is not correctly free'd ------------------------------------- Key: ARQ-444 URL: https://issues.jboss.org/browse/ARQ-444 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Selenium Affects Versions: 1.0.0.Alpha5 Reporter: Karel Piwko Assignee: Karel Piwko @Drone instances stored in method context are not correctly resolved during cleanup leading to opened browsers after test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (ARQ-577) Enhance exception messages for cases where Drone instances cannot be destroyed because no context was created

by Karel Piwko (JIRA)

Enhance exception messages for cases where Drone instances cannot be destroyed because no context was created ------------------------------------------------------------------------------------------------------------- Key: ARQ-577 URL: https://issues.jboss.org/browse/ARQ-577 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: drone_1.0.0.CR2 Reporter: Karel Piwko Priority: Minor Fix For: drone_1.0.0.Final When a deployment fails, during cleanup Drone instance are garbage-collected. There is a check for Drone instance to be null, however it might happen that there is even no context created. If there is no context, Drone throws following NPE: {code} java.lang.NullPointerException at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:82) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:180) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) {code} This NPE should either be wrapped (via Validate utils) or avoided. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-610) Method enrichment does not check for a validity of driver

by Karel Piwko (JIRA)

Method enrichment does not check for a validity of driver --------------------------------------------------------- Key: ARQ-610 URL: https://issues.jboss.org/browse/ARQ-610 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.0.0.CR2 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_1.0.0.Final Consolidate behavior between field and parameter injection. There's a check for configurator existence in field injection, however, it is missing in method parameter injection. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] (ARQ-631) The implementationClass property is ignored when using WebDriver interface as type of selenium instance in tests

by Juraj Huska (Created) (JIRA)

The implementationClass property is ignored when using WebDriver interface as type of selenium instance in tests ---------------------------------------------------------------------------------------------------------------- Key: ARQ-631 URL: https://issues.jboss.org/browse/ARQ-631 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Extension - Drone Affects Versions: drone_1.0.0.CR2 Environment: arquillian-drone-webdriver:CR2 testsuite pom: https://github.com/richfaces/qa/blob/master/showcase-ftest/pom.xml Reporter: Juraj Huska I have this configuration for webdriver in arquillian.xml: {code:xml} <extension qualifier="webdriver"> <property name="implementationClass">org.openqa.selenium.firefox.FirefoxDriver</property> </extension> {code} and this is declaration of my selenium instance: {code} @Drone protected WebDriver webDriver; {code} Since I am not using special properties in arquillian.xml for firefox driver (such as firefoxBinary or firefoxProfile), it should be enough to declare selenium instance with type WebDriver interface. However, in this configuration, it is ignoring the implementationClass property, and *instead of FirefoxDriver it runs default HTMLUnitDriver.* It runs Firefox when the selenium instance is declared with the type FirefoxDriver. -- 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, 7 months

7
6
0 / 0

[JBoss JIRA] Created: (ARQ-611) If Drone extension is on classpath but not used, destroying drone instance will lead to failure

by Karel Piwko (JIRA)

If Drone extension is on classpath but not used, destroying drone instance will lead to failure ----------------------------------------------------------------------------------------------- Key: ARQ-611 URL: https://issues.jboss.org/browse/ARQ-611 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.0.0.CR2 Reporter: Karel Piwko Priority: Critical Fix For: drone_1.0.0.Final {code} java.lang.IllegalArgumentException: Drone context should have been instantiated at org.jboss.arquillian.drone.impl.Validate.notNull(Validate.java:42) at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:180) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (ARQ-599) ApplicationArchiveInstrumenter should also also instrument classes inside JARs

by Marek Schmidt (JIRA)

ApplicationArchiveInstrumenter should also also instrument classes inside JARs ------------------------------------------------------------------------------ Key: ARQ-599 URL: https://issues.jboss.org/browse/ARQ-599 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha1 Reporter: Marek Schmidt Classes inside packaged .jars are not instrumented. ApplicationArchiveInstrumenter should also instrument classes inside archives. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-336) Inject container references in the test to start/stop containers

by Jean Deruelle (JIRA)

Inject container references in the test to start/stop containers ---------------------------------------------------------------- Key: ARQ-336 URL: https://jira.jboss.org/browse/ARQ-336 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Reporter: Jean Deruelle Useful to test HA configuration and failover. Start 3 instances of JBoss AS in cluster mode target one of them and be able to kill it and start new nodes on demand to test failover. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

12
35
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2011