From issues at jboss.org Sat Mar 1 10:23:48 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 1 Mar 2014 10:23:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-1572. --------------------------------- Resolution: Done [Pushed upstrem|https://github.com/arquillian/arquillian-extension-persistence/commit/2609e2579569385526b9a83b144bc255dc357c25] > Marry Persistence and JRebel extensions > --------------------------------------- > > Key: ARQ-1572 > URL: https://issues.jboss.org/browse/ARQ-1572 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bernard Labno > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > JRebel extension currently does not pick up changes in datasets. > Here is how it works: > If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once. > JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*. > Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel. > Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions. > It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes. -- 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 From issues at jboss.org Sat Mar 1 10:23:48 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 1 Mar 2014 10:23:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1646) Add WildFly managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1646 started by Bartosz Majsak. > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sat Mar 1 11:19:47 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 1 Mar 2014 11:19:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1646) Add WildFly managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-1646. --------------------------------- Resolution: Done [Pushed upstream|https://github.com/arquillian/arquillian-extension-persistence/commit/bbd1754e336d067aa9e28b64843cc462933bcca6] > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Mar 2 18:06:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:06:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1327) arquillian-jacoco: Wrong asm library (3.1.1) dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1327: ------------------------------- Fix Version/s: jacoco_1.0.0.Alpha6 > arquillian-jacoco: Wrong asm library (3.1.1) dependency > ------------------------------------------------------- > > Key: ARQ-1327 > URL: https://issues.jboss.org/browse/ARQ-1327 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Tobias Seppenhauser > Fix For: jacoco_1.0.0.Alpha6 > > > In its pom.xml the _arquillian-jacoco_ extension is requiring the _asm_ library in version 3.1.1 > http://search.maven.org/remotecontent?filepath=org/jboss/arquillian/extension/arquillian-jacoco/1.0.0.Alpha5/arquillian-jacoco-1.0.0.Alpha5.pom > The _Jacoco_ libraries itself don't require a certain version of the _asm_ library. > http://search.maven.org/remotecontent?filepath=org/jacoco/org.jacoco.core/0.6.0.201210061924/org.jacoco.core-0.6.0.201210061924.pom > But the problem is, that trying to run a coverage test with _arquillian-jacoco_ and using _asm_ in version 3.1.1 is leading to an {{IncompatibleClassChangeError}}. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} is extending {{org.objectweb.asm.ClassVisitor}}, which is an interface in 3.1.1 and an abstract class in the latest version (4.1). > {code} > public abstract class ClassProbesVisitor extends ClassVisitor { > ... > } > {code} > So, in my opion the asm-depencency should be changed to 4.1 to avoid this error. -- 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 From issues at jboss.org Sun Mar 2 18:10:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:10:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1014) Packaging Processor phase is skipped when the deployment is not testable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1014: ------------------------------- Summary: Packaging Processor phase is skipped when the deployment is not testable (was: Instrumentation is skipped when the deployment is not testable) > Packaging Processor phase is skipped when the deployment is not testable > ------------------------------------------------------------------------ > > Key: ARQ-1014 > URL: https://issues.jboss.org/browse/ARQ-1014 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: 1.0.0.Alpha3 > Reporter: Jan Papousek > Fix For: 2.0.0.Beta1 > > > Documentation of [Deployment|https://github.com/arquillian/arquillian-core/blob/master/container/test-api/src/main/java/org/jboss/arquillian/container/test/api/Deployment.java].testable() says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all [application archive processors|https://github.com/arquillian/arquillian-core/blob/master/container/test-spi/src/main/java/org/jboss/arquillian/container/test/spi/client/deployment/ApplicationArchiveProcessor.java] (see [code|https://github.com/arquillian/arquillian-core/blob/master/container/test-impl-base/src/main/java/org/jboss/arquillian/container/test/impl/client/deployment/DeploymentGenerator.java#L156]), so Jacoco instrumentation is not processed. > I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator. -- 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 From issues at jboss.org Sun Mar 2 18:10:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:10:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1014) Packaging Processor phase is skipped when the deployment is not testable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1014: ------------------------------- Component/s: Packaging Enricher SPI (was: Extension - Jacoco) > Packaging Processor phase is skipped when the deployment is not testable > ------------------------------------------------------------------------ > > Key: ARQ-1014 > URL: https://issues.jboss.org/browse/ARQ-1014 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Packaging Enricher SPI > Affects Versions: 1.0.0.Alpha3 > Reporter: Jan Papousek > Fix For: 2.0.0.Beta1 > > > Documentation of [Deployment|https://github.com/arquillian/arquillian-core/blob/master/container/test-api/src/main/java/org/jboss/arquillian/container/test/api/Deployment.java].testable() says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all [application archive processors|https://github.com/arquillian/arquillian-core/blob/master/container/test-spi/src/main/java/org/jboss/arquillian/container/test/spi/client/deployment/ApplicationArchiveProcessor.java] (see [code|https://github.com/arquillian/arquillian-core/blob/master/container/test-impl-base/src/main/java/org/jboss/arquillian/container/test/impl/client/deployment/DeploymentGenerator.java#L156]), so Jacoco instrumentation is not processed. > I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator. -- 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 From issues at jboss.org Sun Mar 2 18:10:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:10:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1665: ---------------------------------- Summary: Update to Jacoco 0.6.3 Key: ARQ-1665 URL: https://issues.jboss.org/browse/ARQ-1665 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha5 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: jacoco_1.0.0.Alpha6 -- 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 From issues at jboss.org Sun Mar 2 18:10:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:10:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1665: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/12 > Update to Jacoco 0.6.3 > ---------------------- > > Key: ARQ-1665 > URL: https://issues.jboss.org/browse/ARQ-1665 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 18:14:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:14:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1666) Fail to collect coverage data on @Startup annotated EJB's In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1666: ---------------------------------- Summary: Fail to collect coverage data on @Startup annotated EJB's Key: ARQ-1666 URL: https://issues.jboss.org/browse/ARQ-1666 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha5 Reporter: Aslak Knutsen Fix For: jacoco_1.0.0.Alpha6 I have som ejb beans which are marked with @Startup annotation. When I try to run Arquillian tests in managed container and I try to measure code coverage with arquillian jacoco extension I get following exception. {code} 09:27:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10] Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130) at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more Caused by: javax.ejb.EJBException: java.lang.NullPointerException at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 9 more Caused by: java.lang.NullPointerException at org.jboss.arquillian.extension.jacoco.container.ArquillianRuntime.swapExecutionData(ArquillianRuntime.java:78) at pl.borysfan.logic.SomeOtherBean.$jacocoInit(SomeOtherBean.java) at pl.borysfan.logic.SomeOtherBean.(SomeOtherBean.java) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_10] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_10] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_10] at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_10] at java.lang.Class.newInstance0(Class.java:372) [rt.jar:1.7.0_10] at java.lang.Class.newInstance(Class.java:325) [rt.jar:1.7.0_10] at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:100) at org.jboss.as.weld.injection.WeldManagedReferenceFactory.getReference(WeldManagedReferenceFactory.java:77) at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:90) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) ... 18 more {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 From issues at jboss.org Sun Mar 2 18:14:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 18:14:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1666) Fail to collect coverage data on @Startup annotated EJB's In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1666: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/13 > Fail to collect coverage data on @Startup annotated EJB's > --------------------------------------------------------- > > Key: ARQ-1666 > URL: https://issues.jboss.org/browse/ARQ-1666 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > > I have som ejb beans which are marked with @Startup annotation. When I try to run Arquillian tests in managed container and I try to measure code coverage with arquillian jacoco extension I get following exception. > {code} > 09:27:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10] > Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130) > at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > Caused by: javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) > ... 9 more > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.extension.jacoco.container.ArquillianRuntime.swapExecutionData(ArquillianRuntime.java:78) > at pl.borysfan.logic.SomeOtherBean.$jacocoInit(SomeOtherBean.java) > at pl.borysfan.logic.SomeOtherBean.(SomeOtherBean.java) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_10] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_10] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_10] > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance0(Class.java:372) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance(Class.java:325) [rt.jar:1.7.0_10] > at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:100) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.getReference(WeldManagedReferenceFactory.java:77) > at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:90) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) > ... 18 more > {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 From issues at jboss.org Sun Mar 2 19:40:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 19:40:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1387: ------------------------------- Fix Version/s: jacoco_1.0.0.Alpha6 > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Sun Mar 2 19:58:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 19:58:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1387. -------------------------------- Assignee: Aslak Knutsen Resolution: Done upstream: https://github.com/arquillian/arquillian-extension-jacoco/commit/c83ccd5105eaf544997f68345e63308b9a97529a > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Sun Mar 2 19:58:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 19:58:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1327) arquillian-jacoco: Wrong asm library (3.1.1) dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1327. -------------------------------- Assignee: Aslak Knutsen Resolution: Done upstream: https://github.com/arquillian/arquillian-extension-jacoco/commit/595f7de0227ebc14f589e4f4d084f84c48bbb10b > arquillian-jacoco: Wrong asm library (3.1.1) dependency > ------------------------------------------------------- > > Key: ARQ-1327 > URL: https://issues.jboss.org/browse/ARQ-1327 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Tobias Seppenhauser > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > > In its pom.xml the _arquillian-jacoco_ extension is requiring the _asm_ library in version 3.1.1 > http://search.maven.org/remotecontent?filepath=org/jboss/arquillian/extension/arquillian-jacoco/1.0.0.Alpha5/arquillian-jacoco-1.0.0.Alpha5.pom > The _Jacoco_ libraries itself don't require a certain version of the _asm_ library. > http://search.maven.org/remotecontent?filepath=org/jacoco/org.jacoco.core/0.6.0.201210061924/org.jacoco.core-0.6.0.201210061924.pom > But the problem is, that trying to run a coverage test with _arquillian-jacoco_ and using _asm_ in version 3.1.1 is leading to an {{IncompatibleClassChangeError}}. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} is extending {{org.objectweb.asm.ClassVisitor}}, which is an interface in 3.1.1 and an abstract class in the latest version (4.1). > {code} > public abstract class ClassProbesVisitor extends ClassVisitor { > ... > } > {code} > So, in my opion the asm-depencency should be changed to 4.1 to avoid this error. -- 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 From issues at jboss.org Sun Mar 2 19:58:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 19:58:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1665: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done upstream https://github.com/arquillian/arquillian-extension-jacoco/commit/23ca6926c0eabcf52f1ae1b089ed2eeaddd1e6ac > Update to Jacoco 0.6.3 > ---------------------- > > Key: ARQ-1665 > URL: https://issues.jboss.org/browse/ARQ-1665 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 19:58:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 19:58:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1666) Fail to collect coverage data on @Startup annotated EJB's In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1666: ------------------------------- upstream https://github.com/arquillian/arquillian-extension-jacoco/commit/53c6d5bf5da7384c056295e9ff75ad59efc84377 > Fail to collect coverage data on @Startup annotated EJB's > --------------------------------------------------------- > > Key: ARQ-1666 > URL: https://issues.jboss.org/browse/ARQ-1666 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > > I have som ejb beans which are marked with @Startup annotation. When I try to run Arquillian tests in managed container and I try to measure code coverage with arquillian jacoco extension I get following exception. > {code} > 09:27:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10] > Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130) > at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > Caused by: javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) > ... 9 more > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.extension.jacoco.container.ArquillianRuntime.swapExecutionData(ArquillianRuntime.java:78) > at pl.borysfan.logic.SomeOtherBean.$jacocoInit(SomeOtherBean.java) > at pl.borysfan.logic.SomeOtherBean.(SomeOtherBean.java) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_10] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_10] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_10] > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance0(Class.java:372) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance(Class.java:325) [rt.jar:1.7.0_10] > at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:100) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.getReference(WeldManagedReferenceFactory.java:77) > at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:90) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) > ... 18 more > {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 From issues at jboss.org Sun Mar 2 20:04:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:04:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1667) Upgrade to Jacoco 0.6.4 In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1667: ---------------------------------- Summary: Upgrade to Jacoco 0.6.4 Key: ARQ-1667 URL: https://issues.jboss.org/browse/ARQ-1667 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha5 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: jacoco_1.0.0.Alpha6 -- 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 From issues at jboss.org Sun Mar 2 20:06:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:06:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1667) Upgrade to Jacoco 0.6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1667. -------------------------------- Resolution: Done upstream https://github.com/arquillian/arquillian-extension-jacoco/commit/931604eae91abbf6ba61ee5b85794eb6cdc6fc09 > Upgrade to Jacoco 0.6.4 > ----------------------- > > Key: ARQ-1667 > URL: https://issues.jboss.org/browse/ARQ-1667 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 20:26:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:26:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1381) Support Jacoco 0.6.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1381: ------------------------------- Fix Version/s: jacoco_1.0.0.Alpha6 (was: jacoco_1.0.0.next) > Support Jacoco 0.6.2 > -------------------- > > Key: ARQ-1381 > URL: https://issues.jboss.org/browse/ARQ-1381 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Robert Panzer > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 20:28:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1387. ------------------------------ > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Sun Mar 2 20:28:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1327) arquillian-jacoco: Wrong asm library (3.1.1) dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1327. ------------------------------ > arquillian-jacoco: Wrong asm library (3.1.1) dependency > ------------------------------------------------------- > > Key: ARQ-1327 > URL: https://issues.jboss.org/browse/ARQ-1327 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Tobias Seppenhauser > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > > In its pom.xml the _arquillian-jacoco_ extension is requiring the _asm_ library in version 3.1.1 > http://search.maven.org/remotecontent?filepath=org/jboss/arquillian/extension/arquillian-jacoco/1.0.0.Alpha5/arquillian-jacoco-1.0.0.Alpha5.pom > The _Jacoco_ libraries itself don't require a certain version of the _asm_ library. > http://search.maven.org/remotecontent?filepath=org/jacoco/org.jacoco.core/0.6.0.201210061924/org.jacoco.core-0.6.0.201210061924.pom > But the problem is, that trying to run a coverage test with _arquillian-jacoco_ and using _asm_ in version 3.1.1 is leading to an {{IncompatibleClassChangeError}}. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} is extending {{org.objectweb.asm.ClassVisitor}}, which is an interface in 3.1.1 and an abstract class in the latest version (4.1). > {code} > public abstract class ClassProbesVisitor extends ClassVisitor { > ... > } > {code} > So, in my opion the asm-depencency should be changed to 4.1 to avoid this error. -- 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 From issues at jboss.org Sun Mar 2 20:28:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1381) Support Jacoco 0.6.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1381. ------------------------------ > Support Jacoco 0.6.2 > -------------------- > > Key: ARQ-1381 > URL: https://issues.jboss.org/browse/ARQ-1381 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Robert Panzer > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 20:28:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1666) Fail to collect coverage data on @Startup annotated EJB's In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1666. ------------------------------ > Fail to collect coverage data on @Startup annotated EJB's > --------------------------------------------------------- > > Key: ARQ-1666 > URL: https://issues.jboss.org/browse/ARQ-1666 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > > I have som ejb beans which are marked with @Startup annotation. When I try to run Arquillian tests in managed container and I try to measure code coverage with arquillian jacoco extension I get following exception. > {code} > 09:27:08,837 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ear.ear"."logic-0.0.1-SNAPSHOT.jar".component.SomeOtherBean.START: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10] > Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130) > at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > Caused by: javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) > ... 9 more > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.extension.jacoco.container.ArquillianRuntime.swapExecutionData(ArquillianRuntime.java:78) > at pl.borysfan.logic.SomeOtherBean.$jacocoInit(SomeOtherBean.java) > at pl.borysfan.logic.SomeOtherBean.(SomeOtherBean.java) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_10] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_10] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_10] > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance0(Class.java:372) [rt.jar:1.7.0_10] > at java.lang.Class.newInstance(Class.java:325) [rt.jar:1.7.0_10] > at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:100) > at org.jboss.as.weld.injection.WeldManagedReferenceFactory.getReference(WeldManagedReferenceFactory.java:77) > at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:90) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) > ... 18 more > {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 From issues at jboss.org Sun Mar 2 20:28:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1665. ------------------------------ > Update to Jacoco 0.6.3 > ---------------------- > > Key: ARQ-1665 > URL: https://issues.jboss.org/browse/ARQ-1665 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Sun Mar 2 20:28:48 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 2 Mar 2014 20:28:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1667) Upgrade to Jacoco 0.6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1667. ------------------------------ > Upgrade to Jacoco 0.6.4 > ----------------------- > > Key: ARQ-1667 > URL: https://issues.jboss.org/browse/ARQ-1667 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- 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 From issues at jboss.org Mon Mar 3 03:14:48 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 3 Mar 2014 03:14:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-925) Add virgo support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-925. -------------------------------- Resolution: Out of Date Out of Date. Virgo is discontinued - I believe > Add virgo support > ----------------- > > Key: ARQ-925 > URL: https://issues.jboss.org/browse/ARQ-925 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Liu Jianhong > -- 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 From issues at jboss.org Mon Mar 3 03:14:48 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 3 Mar 2014 03:14:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1668) Provide initial version of the embedded equinox container In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1668: ----------------------------------- Summary: Provide initial version of the embedded equinox container Key: ARQ-1668 URL: https://issues.jboss.org/browse/ARQ-1668 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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 From issues at jboss.org Mon Mar 3 03:22:48 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Mon, 3 Mar 2014 03:22:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1668) Provide initial version of the embedded equinox container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1668. --------------------------------- Fix Version/s: osgi_2.0.0.Final Resolution: Done Done in 2.0.0.CR13 Thanks Thorben Janssen > Provide initial version of the embedded equinox container > --------------------------------------------------------- > > Key: ARQ-1668 > URL: https://issues.jboss.org/browse/ARQ-1668 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: osgi_2.0.0.Final > > -- 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 From issues at jboss.org Mon Mar 3 06:10:48 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 06:10:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1655) NPE in WebDriverFactory.createInstance() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1655. ---------------------------- Assignee: Aslak Knutsen Fix Version/s: drone_1.2.4.Final Resolution: Duplicate Issue > NPE in WebDriverFactory.createInstance() > ---------------------------------------- > > Key: ARQ-1655 > URL: https://issues.jboss.org/browse/ARQ-1655 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Juergen Zimmermann > Assignee: Aslak Knutsen > Fix For: drone_1.2.4.Final > > Attachments: arquillian.xml, dependency-tree.txt, stacktrace.txt > > > When I try to run my tests for Firefox (also Chrome and HtmlUnit) I'm getting the attached stacktrace. > I also attach the output of "mvn dependency:tree" and arquillian.xml. > My appserver is WildFly 8.0.0.Final. -- 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 From issues at jboss.org Mon Mar 3 06:12:47 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 3 Mar 2014 06:12:47 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-925) Add virgo support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-925. ----------------------------- > Add virgo support > ----------------- > > Key: ARQ-925 > URL: https://issues.jboss.org/browse/ARQ-925 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Liu Jianhong > -- 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 From issues at jboss.org Mon Mar 3 06:16:50 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 06:16:50 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1653: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: drone_1.2.4.Final > > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-impl/src/main/java/org/jboss/arquillian/drone/impl/DroneInstanceCreator.java#L84 -- 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 From issues at jboss.org Mon Mar 3 06:18:49 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 06:18:49 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Removed temporary workaround for Executor Service In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1669: -------------------------------- Summary: Removed temporary workaround for Executor Service Key: ARQ-1669 URL: https://issues.jboss.org/browse/ARQ-1669 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Reporter: Karel Piwko Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 3 06:18:49 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 06:18:49 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Removed temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1669: ----------------------------- Affects Version/s: drone_1.2.3.Final drone_1.2.4.Final Component/s: Extension - Drone > Removed temporary workaround for Executor Service > ------------------------------------------------- > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 3 06:20:48 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 06:20:48 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Remove temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1669: ----------------------------- Summary: Remove temporary workaround for Executor Service (was: Removed temporary workaround for Executor Service) > Remove temporary workaround for Executor Service > ------------------------------------------------ > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 3 11:12:37 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 11:12:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1634) Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949414#comment-12949414 ] Karel Piwko commented on ARQ-1634: ---------------------------------- Fixed tests in https://github.com/arquillian/arquillian-extension-drone/commit/ead73b71fb7799dd08e2c3408ffeb4122c75ee1f > Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false > --------------------------------------------------------------------------------------- > > Key: ARQ-1634 > URL: https://issues.jboss.org/browse/ARQ-1634 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Environment: Drone 1.2.3.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: drone_1.2.4.Final > > > {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. > It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. > The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _and_. -- 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 From issues at jboss.org Mon Mar 3 11:14:37 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 11:14:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1634) Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1634: ----------------------------- Description: {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _or_. was: {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _and_. > Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false > --------------------------------------------------------------------------------------- > > Key: ARQ-1634 > URL: https://issues.jboss.org/browse/ARQ-1634 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Environment: Drone 1.2.3.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: drone_1.2.4.Final > > > {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. > It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. > The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _or_. -- 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 From issues at jboss.org Mon Mar 3 11:16:38 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 3 Mar 2014 11:16:38 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1009: ----------------------------------- Assignee: Bartosz Majsak > ClassNotFoundException when using CLEAN_INSERT > ---------------------------------------------- > > Key: ARQ-1009 > URL: https://issues.jboss.org/browse/ARQ-1009 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha4 > Environment: Windows 7, Java 1.6.0_31 > Reporter: Karsten Ohme > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > I set in arquillian.xml the configuration property: > CLEAN_INSERT > When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182: > Object instance = Class.forName(value).newInstance(); -- 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 From issues at jboss.org Mon Mar 3 11:24:37 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 3 Mar 2014 11:24:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1634) Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1634: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false > --------------------------------------------------------------------------------------- > > Key: ARQ-1634 > URL: https://issues.jboss.org/browse/ARQ-1634 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Environment: Drone 1.2.3.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: drone_1.2.4.Final > > > {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. > It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. > The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _or_. -- 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 From issues at jboss.org Mon Mar 3 15:10:37 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 3 Mar 2014 15:10:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul reassigned ARQ-1624: --------------------------------- Assignee: Gerhard Poul > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Mon Mar 3 15:14:37 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 3 Mar 2014 15:14:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1624 started by Gerhard Poul. > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Mon Mar 3 15:16:38 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 3 Mar 2014 15:16:38 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949554#comment-12949554 ] Gerhard Poul commented on ARQ-1624: ----------------------------------- Added documentation to the docs: https://docs.jboss.org/author/display/ARQ/WAS+V8.5+-+Remote > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Mon Mar 3 15:28:37 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 3 Mar 2014 15:28:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949556#comment-12949556 ] Gerhard Poul commented on ARQ-1624: ----------------------------------- Pushed this to a test branch at https://github.com/gpoul/arquillian-container-was/tree/ARQ-1624 - waiting for feedback > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Mon Mar 3 16:22:37 2014 From: issues at jboss.org (yangju (JIRA)) Date: Mon, 3 Mar 2014 16:22:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949563#comment-12949563 ] yangju commented on ARQ-1387: ----------------------------- With the latest jacoco_1.0.0.Alpha6, we ran the command "mvn -Pcoverage integration-test and got error like: Error is - Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: java.lang.IncompatibleClassChangeError: class org.jacoco.core.internal.flow.ClassProbesVisitor has interface org.objectweb.asm.ClassVisitor as super class at rg.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125) Please take a look. I am attaching our pom file > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Mon Mar 3 16:22:37 2014 From: issues at jboss.org (yangju (JIRA)) Date: Mon, 3 Mar 2014 16:22:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949564#comment-12949564 ] yangju commented on ARQ-1387: ----------------------------- pom file is below: coverage false arquillian integration org.jboss.as jboss-as-arquillian-container-remote test asm asm org.jboss.arquillian.extension arquillian-jacoco ${arquillian.jacoco.version} test asm asm org.jacoco org.jacoco.core ${jacoco.version} asm asm org.apache.maven.plugins maven-surefire-plugin group-integration integration-test ${arquillian.server.url} ${mongo.host.url} ${redis.host.url} ${argLine} unit-test test test ${maven.test.skip} ${argLine} **/jbossas/** **/selenium/** **/nosql/** **/arquillian/*.* org.apache.maven.plugins maven-failsafe-plugin 2.16 ${skipITs} ${failsafe.argLine} **/arquillian/**.* default-integration-test integration-test integration-test verify verify org.jacoco jacoco-maven-plugin ${jacoco.version} pre-unit-test prepare-agent post-unit-test test report pre-integration-test pre-integration-test prepare-agent-integration ${sonar.jacoco.itReportPath} failsafe.argLine default-report-integration post-integration-test report-integration ${sonar.jacoco.itReportPath} default-check check > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Mon Mar 3 17:54:37 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 3 Mar 2014 17:54:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949568#comment-12949568 ] Aslak Knutsen commented on ARQ-1387: ------------------------------------ I can't see which version of Jacoco you're attempting to use, but it sounds like you're pulling in the wrong version of asm. > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Mon Mar 3 18:22:37 2014 From: issues at jboss.org (yangju (JIRA)) Date: Mon, 3 Mar 2014 18:22:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949573#comment-12949573 ] yangju commented on ARQ-1387: ----------------------------- 1.1.Final-redhat-1 4.1.3.Final-redhat-1 1.0.0.M12-redhat-1 3.1.0.Beta3 2.1.7-redhat-1 1.0.2.Final 2.24.1 2.9.0 0.99 2.2 2.1.2-b04 2.3.3.Final 5.1.4.FINAL-redhat-1 MMMM dd, yyyy 'at' hh:mm aa ${maven.build.timestamp} dev 2.0.0.Alpha1 3.0.0-BETA2 4.4.0-stable 0.6.4.201312101107 Above is all the versions for different artifact but I don't see one defined for ASM. What version we should use for that? > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Mon Mar 3 18:22:37 2014 From: issues at jboss.org (yangju (JIRA)) Date: Mon, 3 Mar 2014 18:22:37 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1387) Support code coverage for jar/war deployed by ZipImporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949574#comment-12949574 ] yangju commented on ARQ-1387: ----------------------------- We actually exclude the asm in the pom. Should we include our own? > Support code coverage for jar/war deployed by ZipImporter > --------------------------------------------------------- > > Key: ARQ-1387 > URL: https://issues.jboss.org/browse/ARQ-1387 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Environment: jdk 1.7, org.jacoco.core.0.6.2.20130203000 > Reporter: Andy Ma > Assignee: Aslak Knutsen > Labels: arquillian-jacoco, jacoco > Fix For: jacoco_1.0.0.Alpha6 > > > If deployed with ZipImporter like: > ShrinkWrap.create(ZipImporter.class, name) > .importFrom(new File(MODULE_PATH + "/" + name)).as(WebArchive.class); > the code coverage of imported archive can not be reported. -- 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 From issues at jboss.org Tue Mar 4 05:33:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Mar 2014 05:33:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1670: -------------------------------------- Summary: Create reporting extension for Arquillian Key: ARQ-1670 URL: https://issues.jboss.org/browse/ARQ-1670 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Reporter: Stefan Miklosovic There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 05:33:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Mar 2014 05:33:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1670: -------------------------------------- Assignee: Stefan Miklosovic > Create reporting extension for Arquillian > ----------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:27:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:27:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1670: ----------------------------- Component/s: Extension - Recorder > Create reporting extension for Arquillian > ----------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:29:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:29:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1670: ----------------------------- Affects Version/s: recorder_1.0.0.Alpha1 > Create reporting extension for Arquillian > ----------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:29:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:29:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1670: ----------------------------- Affects Version/s: (was: recorder_1.0.0.Alpha1) > Create reporting extension for Arquillian > ----------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:29:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:29:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1670: ----------------------------- Fix Version/s: recorder_1.0.0.Alpha1 > Create reporting extension for Arquillian > ----------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha1 > > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create recording & reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1670: ----------------------------- Summary: Create recording & reporting extension for Arquillian (was: Create reporting extension for Arquillian) > Create recording & reporting extension for Arquillian > ----------------------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha1 > > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Tue Mar 4 08:35:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:35:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1638) ChromeDriver binary capability is not propagated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1638. ---------------------------- > ChromeDriver binary capability is not propagated > ------------------------------------------------ > > Key: ARQ-1638 > URL: https://issues.jboss.org/browse/ARQ-1638 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.4.Final > > > Due to double deprecation checks, something a capability might get lost. > For instance: > * configuration contains *chromeBinary* field > * capability is named *chrome.binary* > Hence, when this is set, double deprecation message is emitted but capability is actually never put to map but field is set instead. Factory does not rely on deprecated field, expecting that legacy configurator did the work and value is effectively lost. -- 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 From issues at jboss.org Tue Mar 4 08:35:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:35:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1653. ---------------------------- > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: drone_1.2.4.Final > > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-impl/src/main/java/org/jboss/arquillian/drone/impl/DroneInstanceCreator.java#L84 -- 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 From issues at jboss.org Tue Mar 4 08:35:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:35:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1634) Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1634. ---------------------------- > Automatic augmentation of RemoteWebDriver is not done - canEnhance returns always false > --------------------------------------------------------------------------------------- > > Key: ARQ-1634 > URL: https://issues.jboss.org/browse/ARQ-1634 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Environment: Drone 1.2.3.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: drone_1.2.4.Final > > > {{RemoteWebDriver}} should be augmented automatically, so we can take screenshots from it. > It is not, because {{AugmentingEnhancer#canEnhance}} returns always false. > The cause is on [this|https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/augmentation/AugmentingEnhancer.java#L78] line. According to @kpiwko there should be logical _or_. -- 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 From issues at jboss.org Tue Mar 4 08:35:34 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 4 Mar 2014 08:35:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1544) Drone WebDriver integration with Cukespace breaks in 1.2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1544. ---------------------------- > Drone WebDriver integration with Cukespace breaks in 1.2.0 > ---------------------------------------------------------- > > Key: ARQ-1544 > URL: https://issues.jboss.org/browse/ARQ-1544 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Final > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > Note that it works fine with Drone 1.1.0.Final. It also works with Drone Selenium (DefaultSelenium). > Reproducer: https://github.com/lfryc/cukespace-webdriver > Cukespace issue with details: > https://github.com/cukespace/cukespace/issues/24 > Stack trace: > {code} > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.webdriver.augmentation.AugmentingEnhancer.canEnhance(AugmentingEnhancer.java:75) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:112) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > 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:94) > 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:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > java.lang.RuntimeException > at org.jboss.arquillian.drone.impl.DroneInstanceCreator.createDroneInstance(DroneInstanceCreator.java:96) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.getDroneInstance(DroneTestEnricher.java:111) > at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:72) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > 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:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at cucumber.runtime.arquillian.ArquillianCucumber.access$201(ArquillianCucumber.java:54) > at cucumber.runtime.arquillian.ArquillianCucumber$1.evaluate(ArquillianCucumber.java:91) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > ... > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.getRemoteWebDriverInstantiator(WebDriverFactory.java:153) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:109) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:41) > at org.jboss.arquillian.drone.impl.DroneCallableCreator$1.call(DroneCallableCreator.java:89) > ... > {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 From issues at jboss.org Tue Mar 4 09:13:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 4 Mar 2014 09:13:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1671) Integrate screenshooter implementation to Droidium In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1671: -------------------------------------- Summary: Integrate screenshooter implementation to Droidium Key: ARQ-1671 URL: https://issues.jboss.org/browse/ARQ-1671 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Wed Mar 5 05:10:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 05:10:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1672) Provide default xstl template possibility for screenshooter and recorder implementators In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1672: -------------------------------------- Summary: Provide default xstl template possibility for screenshooter and recorder implementators Key: ARQ-1672 URL: https://issues.jboss.org/browse/ARQ-1672 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic Priority: Minor In case of HTML exporter, template used for XSLT transformation can be configured in arq.xml via property so it is up to user of that extension to come with a custom one. When no such property is defined, default XSLT template bundled in reporter is used - it is also shipped in jar. However, there is no way how to define different default template for screenshooter / recorder implementators so target user would use template of that implementation and not the core one. -- 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 From issues at jboss.org Wed Mar 5 05:12:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 05:12:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1673) Implement asciidoctor exporter for reporter In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1673: -------------------------------------- Summary: Implement asciidoctor exporter for reporter Key: ARQ-1673 URL: https://issues.jboss.org/browse/ARQ-1673 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic Priority: Minor -- 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 From issues at jboss.org Wed Mar 5 05:16:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 05:16:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1674) Investigate implementation of visual feedback of user interaction with application in reports for reporter In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1674: -------------------------------------- Summary: Investigate implementation of visual feedback of user interaction with application in reports for reporter Key: ARQ-1674 URL: https://issues.jboss.org/browse/ARQ-1674 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic It would be handy if user has not only possibility to see screenshots taken before and after test method (and other taken screenshots in a test itself) but he would also see where exactly WebDriver clicked on a page / Android activity. E.g. when user clicks on a button, there would be some red rectangle around it so he would see where exactly test interacted with a tested application. -- 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 From issues at jboss.org Wed Mar 5 05:22:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 05:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1675) Implement multiple file extensions for report type for reporter In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1675: -------------------------------------- Summary: Implement multiple file extensions for report type for reporter Key: ARQ-1675 URL: https://issues.jboss.org/browse/ARQ-1675 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic ReportType class (https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-recorder-reporter/arquillian-recorder-reporter-api/src/main/java/org/arquillian/recorder/reporter/ReportType.java) returns an string of extension report type (which in fact it is the extension of the file). There are some output formats which accepts different extensions, for example valid AsciiDoc extensions are ad, adoc or asciidoc. So it would be a good approach to adapt the interface to allow the definition of multiple extensions. Of course this generates a problem with which exporter to use in case of conflicts: For example one can define: html, html5 and html, html4 and asks for html exporter. I think that in this case the first match should be returned. -- 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 From issues at jboss.org Wed Mar 5 06:14:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 06:14:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1673) Implement asciidoctor exporter for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1673: ----------------------------------- Priority: Major (was: Minor) > Implement asciidoctor exporter for reporter > ------------------------------------------- > > Key: ARQ-1673 > URL: https://issues.jboss.org/browse/ARQ-1673 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > -- 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 From issues at jboss.org Wed Mar 5 06:34:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 06:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1670) Create recording & reporting extension for Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1670. ------------------------------------ Resolution: Done > Create recording & reporting extension for Arquillian > ----------------------------------------------------- > > Key: ARQ-1670 > URL: https://issues.jboss.org/browse/ARQ-1670 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha1 > > > There is not any reporting facility for Arquillian as such - besides plain surefire / junit reports. > It would be useful if screenshots and video records of tests were incorporated to such extension in connectin with reporting of all Arquillian setup in one place, possibly with exporting such report to various output formats (html, xml, json, asciidoc). > Additionally, there is a need to be able to provide single SPI which would any Arquillian extension use in order to report its execution. -- 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 From issues at jboss.org Wed Mar 5 06:34:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 06:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1671) Integrate screenshooter implementation to Droidium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1671: -------------------------------------- Assignee: Stefan Miklosovic > Integrate screenshooter implementation to Droidium > -------------------------------------------------- > > Key: ARQ-1671 > URL: https://issues.jboss.org/browse/ARQ-1671 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- 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 From issues at jboss.org Wed Mar 5 07:00:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 07:00:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1676) Configure frequency of exporting reports for reporting extension In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1676: -------------------------------------- Summary: Configure frequency of exporting reports for reporting extension Key: ARQ-1676 URL: https://issues.jboss.org/browse/ARQ-1676 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic By default, gathered report is exported at the end of the whole Arquillian lifecycle. In case something terrible happens and test does not reach this point and report is gone. It would be useful to provide a configuration option which would say when exactly user wants that report get generated, e.g. after every method or test class. By doing so, even test fatally crashes in the middle, he has at least some knowledge about the test results finished up to that point. -- 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 From issues at jboss.org Wed Mar 5 07:17:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 5 Mar 2014 07:17:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1677: -------------------------------- Summary: Report is not colorblind friendly Key: ARQ-1677 URL: https://issues.jboss.org/browse/ARQ-1677 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Karel Piwko It might be complicated for users to read results of reports. Suggestions to improve: 1/ introduce non-color based symbol for pass (/) and fail (x) 2/ make red brighter and green darker You can follow following references: http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Wed Mar 5 07:27:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 5 Mar 2014 07:27:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1678) Reports are missing "runs as client" for failures In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1678: -------------------------------- Summary: Reports are missing "runs as client" for failures Key: ARQ-1678 URL: https://issues.jboss.org/browse/ARQ-1678 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: recorder_1.0.0.Alpha1 Reporter: Karel Piwko Priority: Minor "runs as client" information is swallowed if exception is raised and test is marked as failed. -- 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 From issues at jboss.org Wed Mar 5 07:29:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 07:29:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950171#comment-12950171 ] Stefan Miklosovic commented on ARQ-1677: ---------------------------------------- Introducing symbols would lead to having pictures which is not desired since it should be just one html and thats it. Usage of blind friendly colors is way to go, in addition with appropriate text added like + and - (plus and minus) symbols to make some difference. > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Wed Mar 5 07:31:33 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 5 Mar 2014 07:31:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1676) Configure frequency of exporting reports for reporting extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950173#comment-12950173 ] Karel Piwko commented on ARQ-1676: ---------------------------------- I believe this is critical issue for Final. Also, I believe this should be done by push model, not pull model, e.g. reporter should react realtime on an event > Configure frequency of exporting reports for reporting extension > ---------------------------------------------------------------- > > Key: ARQ-1676 > URL: https://issues.jboss.org/browse/ARQ-1676 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > > By default, gathered report is exported at the end of the whole Arquillian lifecycle. In case something terrible happens and test does not reach this point and report is gone. It would be useful to provide a configuration option which would say when exactly user wants that report get generated, e.g. after every method or test class. By doing so, even test fatally crashes in the middle, he has at least some knowledge about the test results finished up to that point. -- 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 From issues at jboss.org Wed Mar 5 08:01:36 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 5 Mar 2014 08:01:36 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950185#comment-12950185 ] Karel Piwko commented on ARQ-1677: ---------------------------------- You can easily embed pictures into html ;-) > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Wed Mar 5 08:01:36 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 5 Mar 2014 08:01:36 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950185#comment-12950185 ] Karel Piwko edited comment on ARQ-1677 at 3/5/14 8:01 AM: ---------------------------------------------------------- You can easily embed pictures into html ;-) - http://webcodertools.com/imagetobase64converter was (Author: kpiwko): You can easily embed pictures into html ;-) > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Wed Mar 5 09:13:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 09:13:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1679: -------------------------------------- Summary: When expected exception is thrown in test method, reporter should not report it Key: ARQ-1679 URL: https://issues.jboss.org/browse/ARQ-1679 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic When I have {code} @Test(expected = SomeException.class) public void someTest() { throw new SomeException("this is test exception"); } {code} It should not appear in resulting report. Take JUnit @Rule into account as well. Take into consideration various test frameworks. https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Wed Mar 5 12:11:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 12:11:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1321) Support for HTTPS in URLs injected with @ArquillianResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950365#comment-12950365 ] Stefan Miklosovic commented on ARQ-1321: ---------------------------------------- Hi, I implemented this https://github.com/smiklosovic/arquillian-smart-url feel free to extend. > Support for HTTPS in URLs injected with @ArquillianResource > ----------------------------------------------------------- > > Key: ARQ-1321 > URL: https://issues.jboss.org/browse/ARQ-1321 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Samuel Santos > Assignee: Samuel Santos > > When injecting an URL like the following: > {code:java} > @ArquillianResource URL url; > {code} > HTTP protocol will always be used. This happens because "http" is hard-coded in {{URLResourceProvider}}. > Vineet Reynolds suggested that we can create the type {{SecureUrl}} and a {{SecureUrlResourceProvider}} to allow us to use HTTPS: > {code:java} > @ArquillianResource SecureUrl url; > {code} > Any comment? -- 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 From issues at jboss.org Wed Mar 5 12:19:33 2014 From: issues at jboss.org (Samuel Santos (JIRA)) Date: Wed, 5 Mar 2014 12:19:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1321) Support for HTTPS in URLs injected with @ArquillianResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950369#comment-12950369 ] Samuel Santos commented on ARQ-1321: ------------------------------------ Hi [~smikloso], I've already implemented this locally on Arquillian Core. I'm just waiting for [~aslak] feedback for pushing it upstream. > Support for HTTPS in URLs injected with @ArquillianResource > ----------------------------------------------------------- > > Key: ARQ-1321 > URL: https://issues.jboss.org/browse/ARQ-1321 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Samuel Santos > Assignee: Samuel Santos > > When injecting an URL like the following: > {code:java} > @ArquillianResource URL url; > {code} > HTTP protocol will always be used. This happens because "http" is hard-coded in {{URLResourceProvider}}. > Vineet Reynolds suggested that we can create the type {{SecureUrl}} and a {{SecureUrlResourceProvider}} to allow us to use HTTPS: > {code:java} > @ArquillianResource SecureUrl url; > {code} > Any comment? -- 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 From issues at jboss.org Wed Mar 5 17:13:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 17:13:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1679: -------------------------------------- Assignee: Stefan Miklosovic > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Wed Mar 5 17:13:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 17:13:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1679: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Wed Mar 5 17:15:35 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 17:15:35 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1679. ------------------------------------ Resolution: Done > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Wed Mar 5 18:53:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 18:53:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1676) Configure frequency of exporting reports for reporting extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1676: -------------------------------------- Assignee: Stefan Miklosovic > Configure frequency of exporting reports for reporting extension > ---------------------------------------------------------------- > > Key: ARQ-1676 > URL: https://issues.jboss.org/browse/ARQ-1676 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > By default, gathered report is exported at the end of the whole Arquillian lifecycle. In case something terrible happens and test does not reach this point and report is gone. It would be useful to provide a configuration option which would say when exactly user wants that report get generated, e.g. after every method or test class. By doing so, even test fatally crashes in the middle, he has at least some knowledge about the test results finished up to that point. -- 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 From issues at jboss.org Wed Mar 5 20:45:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 20:45:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1676) Configure frequency of exporting reports for reporting extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1676. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Configure frequency of exporting reports for reporting extension > ---------------------------------------------------------------- > > Key: ARQ-1676 > URL: https://issues.jboss.org/browse/ARQ-1676 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > By default, gathered report is exported at the end of the whole Arquillian lifecycle. In case something terrible happens and test does not reach this point and report is gone. It would be useful to provide a configuration option which would say when exactly user wants that report get generated, e.g. after every method or test class. By doing so, even test fatally crashes in the middle, he has at least some knowledge about the test results finished up to that point. -- 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 From issues at jboss.org Wed Mar 5 20:47:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 20:47:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1675) Implement multiple file extensions for report type for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1675: -------------------------------------- Assignee: Stefan Miklosovic > Implement multiple file extensions for report type for reporter > --------------------------------------------------------------- > > Key: ARQ-1675 > URL: https://issues.jboss.org/browse/ARQ-1675 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > ReportType class (https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-recorder-reporter/arquillian-recorder-reporter-api/src/main/java/org/arquillian/recorder/reporter/ReportType.java) returns an string of extension report type (which in fact it is the extension of the file). There are some output formats which accepts different extensions, for example valid AsciiDoc extensions are ad, adoc or asciidoc. > So it would be a good approach to adapt the interface to allow the definition of multiple extensions. > Of course this generates a problem with which exporter to use in case of conflicts: > For example one can define: > html, html5 > and > html, html4 > and asks for html exporter. I think that in this case the first match should be returned. -- 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 From issues at jboss.org Wed Mar 5 21:23:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 21:23:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1675) Implement multiple file extensions for report type for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1675. ------------------------------------ Resolution: Done > Implement multiple file extensions for report type for reporter > --------------------------------------------------------------- > > Key: ARQ-1675 > URL: https://issues.jboss.org/browse/ARQ-1675 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > ReportType class (https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-recorder-reporter/arquillian-recorder-reporter-api/src/main/java/org/arquillian/recorder/reporter/ReportType.java) returns an string of extension report type (which in fact it is the extension of the file). There are some output formats which accepts different extensions, for example valid AsciiDoc extensions are ad, adoc or asciidoc. > So it would be a good approach to adapt the interface to allow the definition of multiple extensions. > Of course this generates a problem with which exporter to use in case of conflicts: > For example one can define: > html, html5 > and > html, html4 > and asks for html exporter. I think that in this case the first match should be returned. -- 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 From issues at jboss.org Wed Mar 5 21:23:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 21:23:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1675) Implement multiple file extensions for report type for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1675: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > Implement multiple file extensions for report type for reporter > --------------------------------------------------------------- > > Key: ARQ-1675 > URL: https://issues.jboss.org/browse/ARQ-1675 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > ReportType class (https://github.com/arquillian/arquillian-recorder/blob/master/arquillian-recorder-reporter/arquillian-recorder-reporter-api/src/main/java/org/arquillian/recorder/reporter/ReportType.java) returns an string of extension report type (which in fact it is the extension of the file). There are some output formats which accepts different extensions, for example valid AsciiDoc extensions are ad, adoc or asciidoc. > So it would be a good approach to adapt the interface to allow the definition of multiple extensions. > Of course this generates a problem with which exporter to use in case of conflicts: > For example one can define: > html, html5 > and > html, html4 > and asks for html exporter. I think that in this case the first match should be returned. -- 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 From issues at jboss.org Wed Mar 5 21:25:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 5 Mar 2014 21:25:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1677: -------------------------------------- Assignee: Stefan Miklosovic > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Thu Mar 6 05:25:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Mar 2014 05:25:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1677) Report is not colorblind friendly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1677. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Report is not colorblind friendly > --------------------------------- > > Key: ARQ-1677 > URL: https://issues.jboss.org/browse/ARQ-1677 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > It might be complicated for users to read results of reports. > Suggestions to improve: > 1/ introduce non-color based symbol for pass (/) and fail (x) > 2/ make red brighter and green darker > You can follow following references: > http://blog.templatemonster.com/2012/03/21/designing-colorblind-friendly-website/ > https://bugzilla.mozilla.org/show_bug.cgi?id=578994 -- 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 From issues at jboss.org Thu Mar 6 06:07:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Mar 2014 06:07:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1672) Provide default xstl template possibility for screenshooter and recorder implementators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1672: -------------------------------------- Assignee: Stefan Miklosovic > Provide default xstl template possibility for screenshooter and recorder implementators > --------------------------------------------------------------------------------------- > > Key: ARQ-1672 > URL: https://issues.jboss.org/browse/ARQ-1672 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > > In case of HTML exporter, template used for XSLT transformation can be configured in arq.xml via property so it is up to user of that extension to come with a custom one. When no such property is defined, default XSLT template bundled in reporter is used - it is also shipped in jar. > However, there is no way how to define different default template for screenshooter / recorder implementators so target user would use template of that implementation and not the core one. -- 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 From issues at jboss.org Thu Mar 6 06:45:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Mar 2014 06:45:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1672) Provide default xstl template possibility for screenshooter and recorder implementators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1672. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Provide default xstl template possibility for screenshooter and recorder implementators > --------------------------------------------------------------------------------------- > > Key: ARQ-1672 > URL: https://issues.jboss.org/browse/ARQ-1672 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > In case of HTML exporter, template used for XSLT transformation can be configured in arq.xml via property so it is up to user of that extension to come with a custom one. When no such property is defined, default XSLT template bundled in reporter is used - it is also shipped in jar. > However, there is no way how to define different default template for screenshooter / recorder implementators so target user would use template of that implementation and not the core one. -- 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 From issues at jboss.org Thu Mar 6 08:27:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Mar 2014 08:27:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950693#comment-12950693 ] Stefan Miklosovic commented on ARQ-1534: ---------------------------------------- It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly close this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore. > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Thu Mar 6 08:27:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 6 Mar 2014 08:27:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950693#comment-12950693 ] Stefan Miklosovic edited comment on ARQ-1534 at 3/6/14 8:26 AM: ---------------------------------------------------------------- It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly resolve this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore. was (Author: smikloso): It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly close this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore. > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Thu Mar 6 10:30:34 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 10:30:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: Petr Mensik created ARQGRA-424: ---------------------------------- Summary: Graphene is not able to find ParametrizedType deeper in class hierarchy Key: ARQGRA-424 URL: https://issues.jboss.org/browse/ARQGRA-424 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.0.1.Final Reporter: Petr Mensik I ran into this bug when I tried to to have class inheritance like this public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); -- 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 From issues at jboss.org Thu Mar 6 10:34:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 10:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Mensik updated ARQGRA-424: ------------------------------- Description: I ran into this bug when I tried to to have class inheritance like this {code} public class AbstractWebDriverTest

extends Arquillian { }{code} public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); was: I ran into this bug when I tried to to have class inheritance like this public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code} public class AbstractWebDriverTest

extends Arquillian { }{code} > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. > Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); -- 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 From issues at jboss.org Thu Mar 6 10:34:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 10:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Mensik updated ARQGRA-424: ------------------------------- Description: I ran into this bug when I tried to to have class inheritance like this {code} public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } {code} Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); was: I ran into this bug when I tried to to have class inheritance like this {code} public class AbstractWebDriverTest

extends Arquillian { }{code} public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code} public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. > Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); -- 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 From issues at jboss.org Thu Mar 6 10:34:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 10:34:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Mensik updated ARQGRA-424: ------------------------------- Description: I ran into this bug when I tried to to have class inheritance like this {code}public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } {code} Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{code} was: I ran into this bug when I tried to to have class inheritance like this {code} public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } {code} Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method getSuperClassActualTypeArguments in the AbstractSearchContextEnricher. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments(); > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 11:11:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 6 Mar 2014 11:11:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950783#comment-12950783 ] Luk?? Fry? commented on ARQGRA-424: ----------------------------------- [~pmensik] any chance you could put together a fix? > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 11:19:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 11:19:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950794#comment-12950794 ] Petr Mensik commented on ARQGRA-424: ------------------------------------ I am working on that right now:-) > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 11:21:34 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 11:21:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Mensik updated ARQGRA-424: ------------------------------- Description: I ran into this bug when I tried to to have class inheritance like this {code}public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } {code} Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{code} was: I ran into this bug when I tried to to have class inheritance like this {code}public class AbstractWebDriverTest

extends Arquillian { } public class AbstractLanguageTest extends AbstractWebDriverTest { } public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } {code} Code like this will throw an java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in all class in the hierarchy, so this line will give you exception in case of above example. {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{code} > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 12:08:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 12:08:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Mensik updated ARQGRA-424: ------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/97 > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 12:10:33 2014 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Thu, 6 Mar 2014 12:10:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950809#comment-12950809 ] Petr Mensik commented on ARQGRA-424: ------------------------------------ I have added link to the pull request. > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 6 13:15:35 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Thu, 6 Mar 2014 13:15:35 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1516=29_Run?= =?utf-8?q?ning_JUnit_with_Arquillian_on_tomcat_remote_7_tries_to_load_?= =?utf-8?q?=E2=80=A6remote=5F6=2ETomcatRemoteExtension?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Tynj? resolved ARQ-1516. ------------------------------ Assignee: Aslak Knutsen Fix Version/s: tomcat_1.0.0.CR6 Resolution: Done Fixed in CR6: https://github.com/arquillian/arquillian-container-tomcat/commit/3084c7f1be4320cc4e795385e4513f25f6d5a0e0 > Running JUnit with Arquillian on tomcat remote 7 tries to load ?remote_6.TomcatRemoteExtension > ---------------------------------------------------------------------------------------------- > > Key: ARQ-1516 > URL: https://issues.jboss.org/browse/ARQ-1516 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Environment: Windows 7, Tomcat 7.0.42 > Reporter: Petro Verheles > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: tomcat_1.0.0.CR6 > > > Please see the description here > http://stackoverflow.com/questions/19101680/running-junit-with-arquillian-on-tomcat-remote-7-tries-to-load-remote-6-tomca > While browsing the sources of arquillian-tomcat-remote-7-1.0.0.CR5.jar I found that /META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension contains line org.jboss.arquillian.container.tomcat.remote_6.TomcatRemoteExtension. So, I think this is the reason of the bug. Could you please fix ASAP and provide a new version to maven repository? -- 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 From issues at jboss.org Thu Mar 6 13:31:34 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Thu, 6 Mar 2014 13:31:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded should be built against 7.0.52 In-Reply-To: References: Message-ID: Tommy Tynj? created ARQ-1680: -------------------------------- Summary: Tomcat 7 embedded should be built against 7.0.52 Key: ARQ-1680 URL: https://issues.jboss.org/browse/ARQ-1680 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR6 Environment: Tomcat 7.0.52, JDK 1.7 Reporter: Tommy Tynj? Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- 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 From issues at jboss.org Thu Mar 6 13:31:34 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Thu, 6 Mar 2014 13:31:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded should be built against 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Tynj? reassigned ARQ-1680: -------------------------------- Assignee: Tommy Tynj? > Tomcat 7 embedded should be built against 7.0.52 > ------------------------------------------------ > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynj? > Assignee: Tommy Tynj? > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- 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 From issues at jboss.org Thu Mar 6 13:33:33 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Thu, 6 Mar 2014 13:33:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded adapter should be built against 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Tynj? updated ARQ-1680: ----------------------------- Summary: Tomcat 7 embedded adapter should be built against 7.0.52 (was: Tomcat 7 embedded should be built against 7.0.52) > Tomcat 7 embedded adapter should be built against 7.0.52 > -------------------------------------------------------- > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynj? > Assignee: Tommy Tynj? > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- 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 From issues at jboss.org Thu Mar 6 13:39:33 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Thu, 6 Mar 2014 13:39:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded adapter should be built against 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Tynj? updated ARQ-1680: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/22 GitHub pull request sent containing proposed patch. > Tomcat 7 embedded adapter should be built against 7.0.52 > -------------------------------------------------------- > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynj? > Assignee: Tommy Tynj? > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- 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 From issues at jboss.org Fri Mar 7 02:50:33 2014 From: issues at jboss.org (=?UTF-8?Q?Tommy_Tynj=C3=A4_=28JIRA=29?=) Date: Fri, 7 Mar 2014 02:50:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1680) Tomcat 7 embedded adapter should be built against 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Tynj? updated ARQ-1680: ----------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: tomcat_1.0.0.Final Resolution: Done Merged to master: https://github.com/arquillian/arquillian-container-tomcat/pull/22 > Tomcat 7 embedded adapter should be built against 7.0.52 > -------------------------------------------------------- > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynj? > Assignee: Tommy Tynj? > Fix For: tomcat_1.0.0.Final > > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- 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 From issues at jboss.org Fri Mar 7 03:47:33 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 7 Mar 2014 03:47:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: Alex Soto created ARQ-1681: ------------------------------ Summary: Implement multilanguage support in Arquillian Exporter Key: ARQ-1681 URL: https://issues.jboss.org/browse/ARQ-1681 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Alex Soto Priority: Optional Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Fri Mar 7 12:48:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 12:48:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1682) Expose SPI events for ProcessHttpRequest, ProcessWarpRequest and ExecuteWarp In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1682: ------------------------------- Summary: Expose SPI events for ProcessHttpRequest, ProcessWarpRequest and ExecuteWarp Key: ARQ-1682 URL: https://issues.jboss.org/browse/ARQ-1682 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha6 Reporter: Luk?? Fry? -- 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 From issues at jboss.org Fri Mar 7 12:54:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 12:54:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1656) Propogate Contextual operations on HttpFilters In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1656: ---------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: warp_1.0.0.Beta1 Resolution: Done > Propogate Contextual operations on HttpFilters > ---------------------------------------------- > > Key: ARQ-1656 > URL: https://issues.jboss.org/browse/ARQ-1656 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Environment: Arquillian Core 1.1.3 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Beta1 > > > Warp reactivates Context's when creating the client side HttpFilters, but not when executing the actual filtering. > In Arquillian Core 1.1.3 the InheritableThreadLocal were removed which now expose this bug. -- 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 From issues at jboss.org Fri Mar 7 13:00:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:00:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: Luk?? Fry? created ARQ-1683: ------------------------------- Summary: Warp: fails execute on WildFly because mixes up RequestContext objects Key: ARQ-1683 URL: https://issues.jboss.org/browse/ARQ-1683 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha6 Reporter: Luk?? Fry? HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. We are getting this exception: {code} 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] {code} The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:02:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:02:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951258#comment-12951258 ] Luk?? Fry? commented on ARQ-1683: --------------------------------- I have found that by making {{WarpFilter#doFilterWarp}} method {{synchronized}}, the issue disappears. So I guess there can be either an issue how Warp uses RequestContext or it can be bug in thread local implementation of IdBoundContexts in Arquillian Core . > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:04:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:04:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:04:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:04:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Environment: Use following interceptor that will synchronized Warp execution calls: {code} /** * Makes sure that requests are synchronized prevents RF-13530 */ public class WarpRequestSynchronizer { public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { context.proceed(); } } {code} > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Environment: Use following interceptor that will synchronized Warp execution calls: > {code} > /** > * Makes sure that requests are synchronized prevents RF-13530 > */ > public class WarpRequestSynchronizer { > > public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { > context.proceed(); > } > > } > {code} > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:06:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:06:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Environment: (was: Use following interceptor that will synchronized Warp execution calls: {code} /** * Makes sure that requests are synchronized prevents RF-13530 */ public class WarpRequestSynchronizer { public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { context.proceed(); } } {code}) Workaround Description: Use following interceptor that will synchronized Warp execution calls: {code:java} /** * Makes sure that requests are synchronized prevents RF-13530 */ public class WarpRequestSynchronizer { public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { context.proceed(); } } {code} Workaround: Workaround Exists > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:06:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:06:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1682) Expose SPI events for ProcessHttpRequest, ProcessWarpRequest and ExecuteWarp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1682. ----------------------------- Assignee: Luk?? Fry? Fix Version/s: warp_1.0.0.Beta1 Resolution: Done > Expose SPI events for ProcessHttpRequest, ProcessWarpRequest and ExecuteWarp > ---------------------------------------------------------------------------- > > Key: ARQ-1682 > URL: https://issues.jboss.org/browse/ARQ-1682 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > -- 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 From issues at jboss.org Fri Mar 7 13:06:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:06:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951261#comment-12951261 ] Luk?? Fry? commented on ARQ-1683: --------------------------------- I had to expose some SPI events to make the workaround work: ARQ-1682 > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:46:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:46:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Workaround Description: Use following interceptor that will synchronized Warp execution calls: {code:java} public class WarpRequestSynchronizer { public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { context.proceed(); } } {code} https://github.com/richfaces/richfaces/commit/0d8a8fb750ee35cbc74743840035d59706677668 was: Use following interceptor that will synchronized Warp execution calls: {code:java} /** * Makes sure that requests are synchronized prevents RF-13530 */ public class WarpRequestSynchronizer { public synchronized void synchronizedRequests(@Observes(precedence = 100) EventContext context) { context.proceed(); } } {code} > Warp: fails execute on WildFly because mixes up RequestContext objects > ---------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:56:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:56:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because it mixes up RequestContext objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Summary: Warp: fails execute on WildFly because it mixes up RequestContext objects (was: Warp: fails execute on WildFly because mixes up RequestContext objects) > Warp: fails execute on WildFly because it mixes up RequestContext objects > ------------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 13:56:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 13:56:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because it mixes up objects in RequestContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Summary: Warp: fails execute on WildFly because it mixes up objects in RequestContext (was: Warp: fails execute on WildFly because it mixes up RequestContext objects) > Warp: fails execute on WildFly because it mixes up objects in RequestContext > ---------------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 15:10:33 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 7 Mar 2014 15:10:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: fails execute on WildFly because it mixes up objects in RequestContext In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1683. -------------------------------- Assignee: Aslak Knutsen Resolution: Done pushed upstream; https://github.com/arquillian/arquillian-extension-warp/commit/c4fa02dd413619942c53688bd8188ccdff30e083 > Warp: fails execute on WildFly because it mixes up objects in RequestContext > ---------------------------------------------------------------------------- > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Beta1 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Fri Mar 7 15:16:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 15:16:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1560) Having Warp in Classpath causes NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951294#comment-12951294 ] Luk?? Fry? commented on ARQ-1560: --------------------------------- [~templarthelast] any insight? > Having Warp in Classpath causes NPE > ----------------------------------- > > Key: ARQ-1560 > URL: https://issues.jboss.org/browse/ARQ-1560 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Environment: Windows 8 64 Bit Jboss 7.1.1 > Reporter: Lukas Eichler > > This basic test creates a NPE for having Wrap in the classpath and not containing a @Deployment method. Although it isn't a wrap test it gets treated as one. > {code} > @RunWith(Arquillian.class) > public class BasicTest { > @Drone > WebDriver browser; > @ArquillianResource > URL deploymentPath; > @Test > public void firstTest() throws Exception { > browser.navigate().to("http://google.com"); > assertEquals("Google", browser.getTitle()); > } > } > {code} > {code} > Stacktrace > java.lang.NullPointerException > at org.jboss.arquillian.warp.impl.client.proxy.ProxyURLProvider.lookup(ProxyURLProvider.java:70) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.getContextRoot(ContextRootStoreInitializer.java:54) > at org.jboss.arquillian.graphene.location.ContextRootStoreInitializer.setupLocationForClass(ContextRootStoreInitializer.java:47) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:48) > at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > java.lang.IllegalStateException: Unexpected callable present in Drone Context, should be already instantiated at this moment. > at org.jboss.arquillian.drone.impl.InstanceOrCallableInstanceImpl.asInstance(InstanceOrCallableInstanceImpl.java:57) > at org.jboss.arquillian.drone.impl.DroneEnhancer.deenhanceDrone(DroneEnhancer.java:119) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:77) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at com.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:121) > {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 From issues at jboss.org Fri Mar 7 15:18:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 15:18:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1623: ---------------------------- Fix Version/s: warp_1.0.0.Alpha7 (was: warp_1.0.0.Beta1) > Warp: mark tests with category FullEEProfile that will indicate where they can run > ---------------------------------------------------------------------------------- > > Key: ARQ-1623 > URL: https://issues.jboss.org/browse/ARQ-1623 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > E.g. these tests can't run on Tomee: > {code} > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test > {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 From issues at jboss.org Fri Mar 7 15:20:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 15:20:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1535: ---------------------------- Fix Version/s: warp_1.0.0.Alpha7 (was: warp_1.0.0.Beta1) > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > See RF-13222 for issue details. -- 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 From issues at jboss.org Fri Mar 7 15:22:33 2014 From: issues at jboss.org (Rich DiCroce (JIRA)) Date: Fri, 7 Mar 2014 15:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised In-Reply-To: References: Message-ID: Rich DiCroce created ARQ-1684: --------------------------------- Summary: Jacoco extension filters do not work as advertised Key: ARQ-1684 URL: https://issues.jboss.org/browse/ARQ-1684 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha6 Reporter: Rich DiCroce The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-jacoco-1-0-0-Alpha5/] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have exclude some.package.* include some.package.foo.* then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just include my.package.* because of the automatic include all filter, and I can't exclude * include my.package.* because the exclude blocks out the include. Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- 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 From issues at jboss.org Fri Mar 7 15:57:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 15:57:33 -0500 (EST) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1615: ---------------------------- Fix Version/s: warp_1.0.0.Alpha7 (was: warp_1.0.0.Beta1) > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- 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 From issues at jboss.org Fri Mar 7 15:57:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 15:57:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp: response payload was never registered when used with OCPsoft Rewrite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Fix Version/s: warp_1.0.0.Alpha7 (was: warp_1.0.0.Beta1) > Warp: response payload was never registered when used with OCPsoft Rewrite > -------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha7 > > > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Fri Mar 7 16:01:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 16:01:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1498) Warp: get frozen when testing RichFaces FileUpload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1498: ---------------------------- Fix Version/s: warp_1.0.0.Alpha7 (was: warp_1.0.0.Beta1) > Warp: get frozen when testing RichFaces FileUpload > -------------------------------------------------- > > Key: ARQ-1498 > URL: https://issues.jboss.org/browse/ARQ-1498 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha4 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha7 > > > Upstream issue: RF-13217 -- 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 From issues at jboss.org Fri Mar 7 16:11:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 7 Mar 2014 16:11:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1623) Warp: mark tests with category FullEEProfile that will indicate where they can run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1623. ----------------------------- Assignee: Luk?? Fry? Fix Version/s: (was: warp_1.0.0.Alpha7) Resolution: Rejected Yeah, as you said, it's not needed, it works on TomEE just fine: https://arquillian.ci.cloudbees.com/view/Extensions/job/Arquillian-Extension-Warp-Containers/ > Warp: mark tests with category FullEEProfile that will indicate where they can run > ---------------------------------------------------------------------------------- > > Key: ARQ-1623 > URL: https://issues.jboss.org/browse/ARQ-1623 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > E.g. these tests can't run on Tomee: > {code} > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test 0.0 1 > org.jboss.arquillian.warp.ftest.ear.EarWarpTest.test > {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 From issues at jboss.org Sat Mar 8 06:39:33 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 8 Mar 2014 06:39:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: Alex Soto created ARQ-1685: ------------------------------ Summary: Allow user to define when a screenshot is large Key: ARQ-1685 URL: https://issues.jboss.org/browse/ARQ-1685 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sat Mar 8 06:39:33 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 8 Mar 2014 06:39:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-1685: --------------------------- Priority: Minor (was: Major) > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sat Mar 8 09:06:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 09:06:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1685: -------------------------------------- Assignee: Stefan Miklosovic > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sat Mar 8 09:14:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 09:14:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951328#comment-12951328 ] Stefan Miklosovic commented on ARQ-1685: ---------------------------------------- This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sat Mar 8 09:16:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 09:16:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951328#comment-12951328 ] Stefan Miklosovic edited comment on ARQ-1685 at 3/8/14 9:15 AM: ---------------------------------------------------------------- This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. Additionally, the logic behind this was that user can have its own xsl template set in configuration so he modifies it in any way we wants when he is not satisfied with defaults. was (Author: smikloso): This is indeed good point however I do not know what is the best approach in order to pass this information to xslt template. 1) Whole Report could have some "ReportConfiguration" field which would act as metadata for all report so you could extract from there that information easilly. 2) Every screenshot / video report could have boolean displayAsLink property. 3) ? I think that the most wanted option is 1) since it is the most extensionable for the future. We could hook other properties to it quite easilly. > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sat Mar 8 09:22:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 09:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951329#comment-12951329 ] Stefan Miklosovic commented on ARQ-1681: ---------------------------------------- In my opinion, the most doable approach is to have conf property like es which would default to "en" and there would be templates bundled in api jar with all translations so picking the right template is the matter of parsing that property in runtime and picking the right template for that language. In case of providing own languages, the most doable way is to just translate default template to target language and sent a PR. While it is not merge and released, user always can use its own translated template anyway. > Implement multilanguage support in Arquillian Exporter > ------------------------------------------------------ > > Key: ARQ-1681 > URL: https://issues.jboss.org/browse/ARQ-1681 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Alex Soto > Priority: Optional > > Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... > Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. > For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Sat Mar 8 09:22:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 09:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1681: -------------------------------------- Assignee: Stefan Miklosovic > Implement multilanguage support in Arquillian Exporter > ------------------------------------------------------ > > Key: ARQ-1681 > URL: https://issues.jboss.org/browse/ARQ-1681 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Optional > > Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... > Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. > For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Sat Mar 8 12:41:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:41:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951334#comment-12951334 ] Stefan Miklosovic commented on ARQ-1681: ---------------------------------------- https://github.com/arquillian/arquillian-recorder/commit/6d3a0126d1495f04616e9385aa331d8aec9c6d44 in upstream and resolving > Implement multilanguage support in Arquillian Exporter > ------------------------------------------------------ > > Key: ARQ-1681 > URL: https://issues.jboss.org/browse/ARQ-1681 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Optional > > Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... > Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. > For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Sat Mar 8 12:41:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:41:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1681: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > Implement multilanguage support in Arquillian Exporter > ------------------------------------------------------ > > Key: ARQ-1681 > URL: https://issues.jboss.org/browse/ARQ-1681 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Optional > Fix For: recorder_1.0.0.Alpha2 > > > Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... > Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. > For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Sat Mar 8 12:41:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:41:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1681) Implement multilanguage support in Arquillian Exporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1681. ------------------------------------ Resolution: Done > Implement multilanguage support in Arquillian Exporter > ------------------------------------------------------ > > Key: ARQ-1681 > URL: https://issues.jboss.org/browse/ARQ-1681 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Optional > Fix For: recorder_1.0.0.Alpha2 > > > Currently Reports are generated in English. In reports there are some static information like some labels or footnotes, ... > Because test results are also documentation, it has sense that the report may be a part of rendered final documents, but if for example all of them are written in Spanish, then it is strange to have one document in English. > For this reason I think we should add some internal and external default directories where to find translations so people can collaborate in translations, but also allowing users to provide their own. -- 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 From issues at jboss.org Sat Mar 8 12:49:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:49:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1674) Investigate implementation of visual feedback of user interaction with application in reports for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic closed ARQ-1674. ---------------------------------- Resolution: Rejected This is particulary job form implementators (like browser screenshooter from Graphene) and it has nothing to do with core reporter itself. > Investigate implementation of visual feedback of user interaction with application in reports for reporter > ---------------------------------------------------------------------------------------------------------- > > Key: ARQ-1674 > URL: https://issues.jboss.org/browse/ARQ-1674 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > > It would be handy if user has not only possibility to see screenshots taken before and after test method (and other taken screenshots in a test itself) but he would also see where exactly WebDriver clicked on a page / Android activity. > E.g. when user clicks on a button, there would be some red rectangle around it so he would see where exactly test interacted with a tested application. -- 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 From issues at jboss.org Sat Mar 8 12:53:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:53:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reopened ARQ-1679: ------------------------------------ I am reopening this because it does not work with JUnit rules yet. > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Sat Mar 8 12:53:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 12:53:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1679) When expected exception is thrown in test method, reporter should not report it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1679: ----------------------------------- Fix Version/s: (was: recorder_1.0.0.Alpha2) > When expected exception is thrown in test method, reporter should not report it > ------------------------------------------------------------------------------- > > Key: ARQ-1679 > URL: https://issues.jboss.org/browse/ARQ-1679 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > When I have > {code} > @Test(expected = SomeException.class) > public void someTest() { > throw new SomeException("this is test exception"); > } > {code} > It should not appear in resulting report. Take JUnit @Rule into account as well. > Take into consideration various test frameworks. > https://github.com/arquillian/arquillian-recorder/blob/1.0.0.Alpha1/arquillian-recorder-reporter/arquillian-recorder-reporter-impl/src/main/java/org/arquillian/recorder/reporter/impl/ReporterLifecycleObserver.java#L164-L168 -- 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 From issues at jboss.org Sat Mar 8 13:18:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:18:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951337#comment-12951337 ] Stefan Miklosovic commented on ARQ-1581: ---------------------------------------- This was automatically fixed by https://code.google.com/p/android/issues/detail?id=60024 and Droidium has nothing to do here. From what I tested, when you specify ports like --ports 12344,12346 the later one is made odd so it lowers the number by one, so it will be 12344,12345. First number is console port, the second adb port. This is hard time for Android Jenkins plugin since they generate these ports randomly so they need to lower that random number to the non odd in order to get them rightly propagate to plugin specific environment properties. I hence mark this as resolved and wont fix. > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester at fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- 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 From issues at jboss.org Sat Mar 8 13:18:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:18:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1581. ------------------------------------ Resolution: Won't Fix It was automatically resolved by https://code.google.com/p/android/issues/detail?id=60024 > Droidium does not work with remote emulators > -------------------------------------------- > > Key: ARQ-1581 > URL: https://issues.jboss.org/browse/ARQ-1581 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *When*: > I use Android Jenkins Plugin to start the device > *Then*: > It starts the emulator using remote syntax, that is including --port port1,port2 > *Expect*: > Drodium will connect to already running emulator. > *Actual problem*: > AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails. > Output: > {code} > export ANDROID_ADB_SERVER_PORT=52892 > [tester at fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices > List of devices attached > localhost:46689 device > {code} > However, emulators are expected to be in format of emulator-XYZ. > Drodium should be able to modify the behavior to handle this correctly. -- 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 From issues at jboss.org Sat Mar 8 13:22:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:22:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1557) Align undeployment logic in a proper Arquillian way In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1557: -------------------------------------- Assignee: Stefan Miklosovic > Align undeployment logic in a proper Arquillian way > --------------------------------------------------- > > Key: ARQ-1557 > URL: https://issues.jboss.org/browse/ARQ-1557 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Attachments: brainstorming.jpg > > > Right now, undeployment logic for Droidium is bound to observer which observes with precedence -100 on AfterClass event in order to be sure that this observer will be treated as the latest one. > Right now, we have to be sure that undeployment logic is treated lastly in AfterClass since Arquillian Drone destroys WebDriver instances in AfterClass as well and the destruction of WebDriver instance, in our case, means that Selendroid server will be uninstalled from Android device. > Since the destruction of WebDriver instance itself is executed randomly in AfterClass regarding of execution time, we can not do undeployment of APKs on UnDeployDeployment event because when doing so, uninstallation of instrumented APK automatically kills Selendroid server process as well so that in turn means that subsequent trying to destroy WebDriver instance fails since Selendroid server is not running anymore and Drone talks to nobody. > To be sure that all Selendroid servers are uninstalled so we can proceed with the uninstallation of deployments, where it should be done, there has to be a guarantee that all WebDriver instances were already destroyed. > The solution here seems to be quite simple - we put some positive precedence for DroneDestructor (1) however by doing so, it could cause some backward compatibility issues with Drone extension. > (1) https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-impl/src/main/java/org/jboss/arquillian/drone/impl/DroneDestructor.java#L69 -- 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 From issues at jboss.org Sat Mar 8 13:28:33 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:28:33 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951339#comment-12951339 ] Stefan Miklosovic commented on ARQ-1534: ---------------------------------------- https://github.com/arquillian/arquillian-droidium/commit/51d5d96713629031c316f28799129b4ca9637427 > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Sat Mar 8 13:28:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:28:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1534: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Sat Mar 8 13:28:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:28:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1534. ------------------------------------ Resolution: Done > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Sat Mar 8 13:28:34 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 8 Mar 2014 13:28:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1534: ----------------------------------- Comment: was deleted (was: It was (finally) included in ddmlib 22.7.0 when it was merged. I gladly resolve this. By default, port is set to 5038. System default is 5037 so started test will not polute eclipse logger anymore.) > There is no way how to set server port of Android Debug Bridge > -------------------------------------------------------------- > > Key: ARQ-1534 > URL: https://issues.jboss.org/browse/ARQ-1534 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > *Given*: > I have Android tooling installed in Eclipse/JBDS. > *When:* > I use Droidium in tests fro IDE. > *Expect*: > No having any errors in DDMS output in IDE. > *Additional information*: > It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly. > See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037. > We need a way how to change this server port in Droidium configuration. -- 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 From issues at jboss.org Sat Mar 8 13:28:34 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 8 Mar 2014 13:28:34 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951340#comment-12951340 ] Alex Soto commented on ARQ-1685: -------------------------------- I completely agree that the first option is the best one. Moreover values like height and size could be take in consideration. > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Sun Mar 9 10:42:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 10:42:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1440) Performance drops > 300% In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-1440. --------------------------------- Resolution: Done > Performance drops > 300% > ------------------------ > > Key: ARQ-1440 > URL: https://issues.jboss.org/browse/ARQ-1440 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6 > Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3 > Reporter: Noah White > Assignee: Bartosz Majsak > Priority: Critical > Fix For: persistence_1.0.0.next > > > I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment. > For example one test which took 13s to run in the old environment now takes 44s. > This slow down only seems to affect tests which use the persistence extension. > Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests. -- 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 From issues at jboss.org Sun Mar 9 12:52:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 12:52:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-1009. --------------------------------- Resolution: Won't Fix As already mentioned by [~brzhk] configuration is case sensitive. To be precise it is 1-1 mapping between the fields exposed by configuration objects to property names in the XML file. I have lately introduced warning message which is prompted when there is no match with the corresponding configuration. Pushed upstream [@8a98920|https://github.com/arquillian/arquillian-extension-persistence/commit/8a989200d2128e8feee42d6894ad8a6754740180]. > ClassNotFoundException when using CLEAN_INSERT > ---------------------------------------------- > > Key: ARQ-1009 > URL: https://issues.jboss.org/browse/ARQ-1009 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha4 > Environment: Windows 7, Java 1.6.0_31 > Reporter: Karsten Ohme > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > I set in arquillian.xml the configuration property: > CLEAN_INSERT > When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182: > Object instance = Class.forName(value).newInstance(); -- 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 From issues at jboss.org Sun Mar 9 13:35:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 13:35:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1147) Improve the column filtering feature to use custom IColumnFilter implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1147: ----------------------------------- Assignee: Bartosz Majsak (was: Vineet Reynolds) > Improve the column filtering feature to use custom IColumnFilter implementations > -------------------------------------------------------------------------------- > > Key: ARQ-1147 > URL: https://issues.jboss.org/browse/ARQ-1147 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Vineet Reynolds > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > For now, APE implements column filtering based on column names specified in the {{excludeColumns}} attribute of the {{@ShouldMatchDataSet}} annotation (introduced in ARQ-772). This could be extended to allow custom {{IColumnFilter}} implementations to be plugged in during the verification phase. > The use of {{IColumnFilter}} implementations is described here: http://www.dbunit.org/faq.html#columnfilter -- 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 From issues at jboss.org Sun Mar 9 13:35:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 13:35:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1147) Improve the column filtering feature to use custom IColumnFilter implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1147 started by Bartosz Majsak. > Improve the column filtering feature to use custom IColumnFilter implementations > -------------------------------------------------------------------------------- > > Key: ARQ-1147 > URL: https://issues.jboss.org/browse/ARQ-1147 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Vineet Reynolds > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > For now, APE implements column filtering based on column names specified in the {{excludeColumns}} attribute of the {{@ShouldMatchDataSet}} annotation (introduced in ARQ-772). This could be extended to allow custom {{IColumnFilter}} implementations to be plugged in during the verification phase. > The use of {{IColumnFilter}} implementations is described here: http://www.dbunit.org/faq.html#columnfilter -- 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 From issues at jboss.org Sun Mar 9 16:54:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 16:54:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-812: ------------------------------- Description: Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. (was: Introduce SPIs for core functionalities.) > Split DBUnit and Core implemenation > ----------------------------------- > > Key: ARQ-812 > URL: https://issues.jboss.org/browse/ARQ-812 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. -- 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 From issues at jboss.org Sun Mar 9 16:56:33 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sun, 9 Mar 2014 16:56:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-812: ------------------------------- Fix Version/s: persistence_1.0.0.next > Split DBUnit and Core implemenation > ----------------------------------- > > Key: ARQ-812 > URL: https://issues.jboss.org/browse/ARQ-812 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. -- 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 From issues at jboss.org Sun Mar 9 19:50:33 2014 From: issues at jboss.org (Tair Sabirgaliev (JIRA)) Date: Sun, 9 Mar 2014 19:50:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1686) Make testRunnerAdapter.test(...) more flexible In-Reply-To: References: Message-ID: Tair Sabirgaliev created ARQ-1686: ------------------------------------- Summary: Make testRunnerAdapter.test(...) more flexible Key: ARQ-1686 URL: https://issues.jboss.org/browse/ARQ-1686 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Test Protocol SPIs and Implementation Affects Versions: 1.1.3.Final Reporter: Tair Sabirgaliev Priority: Minor On client side a test case in a test class is represented by java.lang.reflect.Method. This makes impossible to easily integrate frameworks like ScalaTest, where a test case is not necessarily a class method. As a solution, it would be great to: (a) relax the test representation to just a String identifier, and leave the interpretation to relevant TestRunner implementation (which is already the case?) (b) be able to pass optional params at testRunnerAdapter.test(...), so that they are transmitted to container side as additional hints. Map would be good enough. -- 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 From issues at jboss.org Sun Mar 9 20:26:33 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 9 Mar 2014 20:26:33 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1686) Make testRunnerAdapter.test(...) more flexible In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1686: ------------------------------- Fix Version/s: 2.0.0.Beta1 > Make testRunnerAdapter.test(...) more flexible > ---------------------------------------------- > > Key: ARQ-1686 > URL: https://issues.jboss.org/browse/ARQ-1686 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.1.3.Final > Reporter: Tair Sabirgaliev > Priority: Minor > Fix For: 2.0.0.Beta1 > > > On client side a test case in a test class is represented by java.lang.reflect.Method. This makes impossible to easily integrate frameworks like ScalaTest, where a test case is not necessarily a class method. > As a solution, it would be great to: > (a) relax the test representation to just a String identifier, and leave the interpretation to relevant TestRunner implementation (which is already the case?) > (b) be able to pass optional params at testRunnerAdapter.test(...), so that they are transmitted to container side as additional hints. Map would be good enough. -- 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 From issues at jboss.org Mon Mar 10 03:39:10 2014 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Mon, 10 Mar 2014 03:39:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-812) Split DBUnit and Core implemenation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak resolved ARQ-812. -------------------------------- Resolution: Done [Pushed upstream.|https://github.com/arquillian/arquillian-extension-persistence/commit/9035d60c77fc8bef341b7031c11d7a1870ef55d1] > Split DBUnit and Core implemenation > ----------------------------------- > > Key: ARQ-812 > URL: https://issues.jboss.org/browse/ARQ-812 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > Split Core and DBUnit modules in order to prepare the ground for extension model which will open integration with other tools such as Liquibase. -- 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 From issues at jboss.org Mon Mar 10 08:01:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 08:01:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1687) Support setting process basedir In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1687: -------------------------------- Summary: Support setting process basedir Key: ARQ-1687 URL: https://issues.jboss.org/browse/ARQ-1687 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha1 Reporter: Karel Piwko Is is not possible to setup a home directory of spawned/executed process. -- 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 From issues at jboss.org Mon Mar 10 08:03:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 08:03:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1687) Support setting process basedir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1687: ----------------------------- Assignee: Tadeas Kriz > Support setting process basedir > ------------------------------- > > Key: ARQ-1687 > URL: https://issues.jboss.org/browse/ARQ-1687 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > > Is is not possible to setup a home directory of spawned/executed process. -- 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 From issues at jboss.org Mon Mar 10 08:13:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 08:13:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1687) Support setting process basedir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1687. ------------------------------ Fix Version/s: spacelift_1.0.0.Alpha2 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-spacelift/commit/b329696a8c477e90f9e5002656a06cc4f2d5a398 > Support setting process basedir > ------------------------------- > > Key: ARQ-1687 > URL: https://issues.jboss.org/browse/ARQ-1687 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: spacelift_1.0.0.Alpha2 > > > Is is not possible to setup a home directory of spawned/executed process. -- 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 From issues at jboss.org Mon Mar 10 09:03:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 09:03:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-927) Configuration for RemoteWebDriver Drone extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-927: ----------------------------- Reopened to fix affects version. > Configuration for RemoteWebDriver Drone extension > ------------------------------------------------- > > Key: ARQ-927 > URL: https://issues.jboss.org/browse/ARQ-927 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.next > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Fix For: drone_1.1.0.CR1 > > > See top-level task for details of reusable session feature. > ---- > The support for RemoteWebDriver should be part of Drone, including configuration, but it has been prototyped in Graphene, to allow introduce the feature quickly. > Right now, configuration is hard-coded to Firefox: > https://github.com/arquillian/arquillian-graphene/blob/feature/quick-turnaround/graphene-webdriver-drone/src/main/java/org/jboss/arquillian/graphene/drone/factory/RemoteWebDriverFactory.java#L78 > Allow to configure the {{RemoteWebDriver}} browser in {{arquillian.xml}}. > ---- > The {{RemoteWebDriver}} configuration differs from other types. > ---- > If necessary, {{RemoteWebDriver}} can be moved to Drone at this point and whole configuration might be addressed there. -- 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 From issues at jboss.org Mon Mar 10 09:03:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 09:03:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-927) Configuration for RemoteWebDriver Drone extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-927: ---------------------------- Affects Version/s: (was: drone_1.2.next) > Configuration for RemoteWebDriver Drone extension > ------------------------------------------------- > > Key: ARQ-927 > URL: https://issues.jboss.org/browse/ARQ-927 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Fix For: drone_1.1.0.CR1 > > > See top-level task for details of reusable session feature. > ---- > The support for RemoteWebDriver should be part of Drone, including configuration, but it has been prototyped in Graphene, to allow introduce the feature quickly. > Right now, configuration is hard-coded to Firefox: > https://github.com/arquillian/arquillian-graphene/blob/feature/quick-turnaround/graphene-webdriver-drone/src/main/java/org/jboss/arquillian/graphene/drone/factory/RemoteWebDriverFactory.java#L78 > Allow to configure the {{RemoteWebDriver}} browser in {{arquillian.xml}}. > ---- > The {{RemoteWebDriver}} configuration differs from other types. > ---- > If necessary, {{RemoteWebDriver}} can be moved to Drone at this point and whole configuration might be addressed there. -- 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 From issues at jboss.org Mon Mar 10 09:03:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 09:03:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-927) Configuration for RemoteWebDriver Drone extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-927. ----------------------------- Resolution: Done > Configuration for RemoteWebDriver Drone extension > ------------------------------------------------- > > Key: ARQ-927 > URL: https://issues.jboss.org/browse/ARQ-927 > Project: Arquillian > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Assignee: Jan Papousek > Fix For: drone_1.1.0.CR1 > > > See top-level task for details of reusable session feature. > ---- > The support for RemoteWebDriver should be part of Drone, including configuration, but it has been prototyped in Graphene, to allow introduce the feature quickly. > Right now, configuration is hard-coded to Firefox: > https://github.com/arquillian/arquillian-graphene/blob/feature/quick-turnaround/graphene-webdriver-drone/src/main/java/org/jboss/arquillian/graphene/drone/factory/RemoteWebDriverFactory.java#L78 > Allow to configure the {{RemoteWebDriver}} browser in {{arquillian.xml}}. > ---- > The {{RemoteWebDriver}} configuration differs from other types. > ---- > If necessary, {{RemoteWebDriver}} can be moved to Drone at this point and whole configuration might be addressed there. -- 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 From issues at jboss.org Mon Mar 10 09:05:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 09:05:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-437) Introduce annotation to control lifecycle of selenium session In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-437: ---------------------------- Fix Version/s: drone_2.0.0.Alpha1 (was: drone_1.4.next) > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Fix For: drone_2.0.0.Alpha1 > > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- 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 From issues at jboss.org Mon Mar 10 11:03:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:03:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1688) Drop Selenium 1.0 support In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1688: -------------------------------- Summary: Drop Selenium 1.0 support Key: ARQ-1688 URL: https://issues.jboss.org/browse/ARQ-1688 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Drop Selenium 1.0 altogether from Drone. -- 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 From issues at jboss.org Mon Mar 10 11:03:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:03:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1688) Drop Selenium 1.0 support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1688: ----------------------------- Fix Version/s: drone_2.0.0.Alpha1 > Drop Selenium 1.0 support > ------------------------- > > Key: ARQ-1688 > URL: https://issues.jboss.org/browse/ARQ-1688 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Drop Selenium 1.0 altogether from Drone. -- 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 From issues at jboss.org Mon Mar 10 11:05:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:05:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1689) Drop Android and iOS Drivers In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1689: -------------------------------- Summary: Drop Android and iOS Drivers Key: ARQ-1689 URL: https://issues.jboss.org/browse/ARQ-1689 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Drop AndroidDriver and iPhoneDriver, as they were dropped from upstream Selenium. -- 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 From issues at jboss.org Mon Mar 10 11:09:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:09:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1690) Provide and API/SPI to solve backward compatibility In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1690: -------------------------------- Summary: Provide and API/SPI to solve backward compatibility Key: ARQ-1690 URL: https://issues.jboss.org/browse/ARQ-1690 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha2 For extension relying on Drone 1.2.x, migration to 2.0.0 should be smooth. Identify what API/SPI needs to be supported based on existing extensions: These are at least: * Graphene 2 * Warp * JBehave * CukeSpace * APE * SauceLabs Note, likely we won't be able to support backwards compatibility 100%. We rather need to make sure major extensions using Drone stay compatible or provide a very easy migration path, e.g. Drone compatibility package. -- 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 From issues at jboss.org Mon Mar 10 11:09:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:09:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1691) Flexible model for browsers SPI In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1691: -------------------------------- Summary: Flexible model for browsers SPI Key: ARQ-1691 URL: https://issues.jboss.org/browse/ARQ-1691 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha2 Ensure that adding new browser, either via Drone Extension or via a separate extension is super easy. For instance, Droidium will need to provide "android" browser. -- 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 From issues at jboss.org Mon Mar 10 11:11:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:11:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1692) Factories should not bring runtime dependencies In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1692: -------------------------------- Summary: Factories should not bring runtime dependencies Key: ARQ-1692 URL: https://issues.jboss.org/browse/ARQ-1692 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha2 DroneFactories should fail graciously in case that Drone type they are trying to instantiate are not on classpath. -- 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 From issues at jboss.org Mon Mar 10 11:13:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:13:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1693) Independent and flexible lifecycle for Drones In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1693: -------------------------------- Summary: Independent and flexible lifecycle for Drones Key: ARQ-1693 URL: https://issues.jboss.org/browse/ARQ-1693 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha3 It should be possible to define lifecycle that is independent of existing Arquillian events. Suite being one of the most prominent ones. -- 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 From issues at jboss.org Mon Mar 10 11:13:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:13:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1694) Update Saucelabs extension In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1694: -------------------------------- Summary: Update Saucelabs extension Key: ARQ-1694 URL: https://issues.jboss.org/browse/ARQ-1694 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha3 Provide working SauceLabs extension fully compatible with Drone 2. -- 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 From issues at jboss.org Mon Mar 10 11:15:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:15:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1695) Integrate Spacelift into Drone In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1695: -------------------------------- Summary: Integrate Spacelift into Drone Key: ARQ-1695 URL: https://issues.jboss.org/browse/ARQ-1695 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Alpha3 Spacelift can be used for following tasks: * Download and execution of Selenium Server * Download of ChromeDriver binary * Download of IEDriver binary (optional, might not be needed as of IE11+) -- 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 From issues at jboss.org Mon Mar 10 11:17:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:17:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1696) Update documentation to cover Drone 2.0.0 In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1696: -------------------------------- Summary: Update documentation to cover Drone 2.0.0 Key: ARQ-1696 URL: https://issues.jboss.org/browse/ARQ-1696 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Beta1 Update documentation to cover Arquillian Drone 2.0.0. Graphene 2 being the most prominent citizen here. -- 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 From issues at jboss.org Mon Mar 10 11:17:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:17:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1697) Migration guide for users In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1697: -------------------------------- Summary: Migration guide for users Key: ARQ-1697 URL: https://issues.jboss.org/browse/ARQ-1697 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Beta1 Provide a migration guide to help users use Drone 2.0.0 instead of 1.2.x/1.3.x. -- 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 From issues at jboss.org Mon Mar 10 11:17:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:17:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1698) Migration guide for developers In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1698: -------------------------------- Summary: Migration guide for developers Key: ARQ-1698 URL: https://issues.jboss.org/browse/ARQ-1698 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Beta1 Provide a migration guide for developers updating their extensions from 1.2/1.3 to 2.0. -- 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 From issues at jboss.org Mon Mar 10 11:19:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:19:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by Spacelift In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1699: -------------------------------- Summary: PhantomJS resolution by Spacelift Key: ARQ-1699 URL: https://issues.jboss.org/browse/ARQ-1699 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Fix For: drone_2.0.0.Beta1 PhantomJS resolution should be done via Spacelift. -- 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 From issues at jboss.org Mon Mar 10 11:21:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 10 Mar 2014 11:21:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1700) Provide Deployment scope support for Drone In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1700: -------------------------------- Summary: Provide Deployment scope support for Drone Key: ARQ-1700 URL: https://issues.jboss.org/browse/ARQ-1700 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Assignee: Tadeas Kriz Fix For: drone_2.0.0.Alpha1 For Droidium and iOSium containers, there should be a support for @Deployment based scopes. This is a foundation for Drone 2.0.0. -- 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 From issues at jboss.org Mon Mar 10 12:05:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 10 Mar 2014 12:05:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1498) Warp: get frozen when testing RichFaces FileUpload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951650#comment-12951650 ] Luk?? Fry? commented on ARQ-1498: --------------------------------- As I described in [RF-13217|https://issues.jboss.org/browse/RF-13217?focusedCommentId=12951646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12951646], this is not Warp's issue as it works fine with Firefox. > Warp: get frozen when testing RichFaces FileUpload > -------------------------------------------------- > > Key: ARQ-1498 > URL: https://issues.jboss.org/browse/ARQ-1498 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha4 > Reporter: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha7 > > > Upstream issue: RF-13217 -- 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 From issues at jboss.org Mon Mar 10 12:05:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 10 Mar 2014 12:05:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1498) Warp: get frozen when testing RichFaces FileUpload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1498. ----------------------------- Assignee: Luk?? Fry? Fix Version/s: (was: warp_1.0.0.Alpha7) Resolution: Rejected > Warp: get frozen when testing RichFaces FileUpload > -------------------------------------------------- > > Key: ARQ-1498 > URL: https://issues.jboss.org/browse/ARQ-1498 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > > Upstream issue: RF-13217 -- 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 From issues at jboss.org Mon Mar 10 13:11:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 10 Mar 2014 13:11:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951669#comment-12951669 ] Stefan Miklosovic commented on ARQ-1685: ---------------------------------------- in upstream and resolving as done https://github.com/arquillian/arquillian-recorder/commit/d322d93f46180a704cd9efabe49c23fe5e939132 > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Mon Mar 10 13:11:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 10 Mar 2014 13:11:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1685) Allow user to define when a screenshot is large In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1685. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Allow user to define when a screenshot is large > ----------------------------------------------- > > Key: ARQ-1685 > URL: https://issues.jboss.org/browse/ARQ-1685 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > In Arquillian reporter when an image is large than 500px width, it is considered large, and instead of embedding inside report, a link is added. I think it should be useful to decide to final user if 500px width is large or not. -- 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 From issues at jboss.org Tue Mar 11 04:51:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 04:51:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-420) Port unified screenshooter implementation for Graphene into Graphene project itself In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned ARQGRA-420: ---------------------------------- Assignee: Juraj H?ska (was: Stefan Miklosovic) > Port unified screenshooter implementation for Graphene into Graphene project itself > ----------------------------------------------------------------------------------- > > Key: ARQGRA-420 > URL: https://issues.jboss.org/browse/ARQGRA-420 > Project: Arquillian Graphene > Issue Type: Task > Components: api, build, core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 2.1-Tracking > > > Port screenshooter implementation from unified screenshooter repository, [here|https://github.com/smiklosovic/arquillian-unified-recorder/tree/master/implementations/arquillian-browser-screenshooter], > into Graphene project repository. -- 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 From issues at jboss.org Tue Mar 11 05:55:10 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 11 Mar 2014 05:55:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: Alex Soto created ARQ-1701: ------------------------------ Summary: Allow possibility to resize screenshots Key: ARQ-1701 URL: https://issues.jboss.org/browse/ARQ-1701 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Tue Mar 11 06:07:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 06:07:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951858#comment-12951858 ] Stefan Miklosovic commented on ARQ-1701: ---------------------------------------- Feel free to implement this. > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Tue Mar 11 06:09:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 06:09:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951858#comment-12951858 ] Stefan Miklosovic edited comment on ARQ-1701 at 3/11/14 6:08 AM: ----------------------------------------------------------------- Feel free to implement this. This could be extended to videos as well. was (Author: smikloso): Feel free to implement this. > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Tue Mar 11 06:17:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:17:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-425: ---------------------------------- Summary: Allow @Location with relative URL when there is no deployment Key: ARQGRA-425 URL: https://issues.jboss.org/browse/ARQGRA-425 Project: Arquillian Graphene Issue Type: Feature Request Components: core Affects Versions: 2.0.1.Final Reporter: Juraj H?ska There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. As [~kpiwko] suggested, we can support his in Graphene like this: # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null # make that value configurable via Graphene configuration [~lfryc] Please, what do you think about this addition ? -- 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 From issues at jboss.org Tue Mar 11 06:19:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:19:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-425: ------------------------------- Description: There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. As [~kpiwko] suggested, we can support his in Graphene like this: # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null # make that value configurable via Graphene configuration was: There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. As [~kpiwko] suggested, we can support his in Graphene like this: # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null # make that value configurable via Graphene configuration [~lfryc] Please, what do you think about this addition ? > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 06:19:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:19:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951862#comment-12951862 ] Juraj H?ska commented on ARQGRA-425: ------------------------------------ [~lfryc] Please, what do you think about this addition ? > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 06:19:11 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 11 Mar 2014 06:19:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1702) Add optional label for report title In-Reply-To: References: Message-ID: Alex Soto created ARQ-1702: ------------------------------ Summary: Add optional label for report title Key: ARQ-1702 URL: https://issues.jboss.org/browse/ARQ-1702 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like: Tests results under ${env} So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title. -- 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 From issues at jboss.org Tue Mar 11 06:21:10 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 11 Mar 2014 06:21:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951866#comment-12951866 ] Alex Soto commented on ARQ-1701: -------------------------------- Ok I am not sure when I will have time to do it but I try it as soon as possible. Maybe for JavaLand hackergarten. > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Tue Mar 11 06:21:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:21:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951867#comment-12951867 ] Juraj H?ska commented on ARQGRA-425: ------------------------------------ [~smikloso] is playing nicely with URL in https://github.com/smiklosovic/arquillian-smart-url. We might reuse something from that solution. > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 06:37:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:37:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951871#comment-12951871 ] Luk?? Fry? commented on ARQGRA-425: ----------------------------------- Right, we need to provide own wrapper for URLResourceProvider +1 this will be nice addition > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 06:37:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:37:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951872#comment-12951872 ] Luk?? Fry? commented on ARQGRA-425: ----------------------------------- I would vote for implementing it on 2.1 branch > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 06:39:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 06:39:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-425: ------------------------------ Fix Version/s: 2.1-Tracking > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Tue Mar 11 07:09:11 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 11 Mar 2014 07:09:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report In-Reply-To: References: Message-ID: Alex Soto created ARQ-1703: ------------------------------ Summary: Add annotation to add comments to test report Key: ARQ-1703 URL: https://issues.jboss.org/browse/ARQ-1703 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part. So it would be good if for example we could annotate test method with an annotation like: @Report("This test should be executed manually too") And then this message may be available on reporter class and could be written to report. -- 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 From issues at jboss.org Tue Mar 11 08:45:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 08:45:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQ-1535: ------------------------------- Assignee: Luk?? Fry? > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > See RF-13222 for issue details. -- 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 From issues at jboss.org Tue Mar 11 08:51:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 08:51:10 -0400 (EDT) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQ-1615: ------------------------------- Assignee: Luk?? Fry? > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- 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 From issues at jboss.org Tue Mar 11 08:51:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 08:51:10 -0400 (EDT) Subject: [arquillian-issues] =?utf-8?q?=5BJBoss_JIRA=5D_=28ARQ-1615=29_War?= =?utf-8?q?p_JSF=3A_detect_and_sanitize_FacesContextWrapper=C2=A0chain?= In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1615. ----------------------------- Resolution: Done > Warp JSF: detect and sanitize FacesContextWrapper?chain > ------------------------------------------------------- > > Key: ARQ-1615 > URL: https://issues.jboss.org/browse/ARQ-1615 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha5 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > When there is a chain of {{FacesContextWrapper}}s then Warp's WrappedFacesContext might fail to be detected and Warp itself may fail. > Use a while loop to iterate through wrappers in order to detect correct wrapper. > Needs to be accompanied with a ftest. -- 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 From issues at jboss.org Tue Mar 11 09:33:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 09:33:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1535. ----------------------------- Resolution: Rejected Probably fixed by ARQ-1683 > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > See RF-13222 for issue details. -- 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 From issues at jboss.org Tue Mar 11 09:57:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 11 Mar 2014 09:57:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951984#comment-12951984 ] Karel Piwko commented on ARQ-1703: ---------------------------------- This is great idea. > Add annotation to add comments to test report > --------------------------------------------- > > Key: ARQ-1703 > URL: https://issues.jboss.org/browse/ARQ-1703 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part. > So it would be good if for example we could annotate test method with an annotation like: > @Report("This test should be executed manually too") > And then this message may be available on reporter class and could be written to report. -- 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 From issues at jboss.org Tue Mar 11 10:34:04 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 10:34:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952003#comment-12952003 ] Stefan Miklosovic commented on ARQ-1703: ---------------------------------------- in upstream and resolving https://github.com/arquillian/arquillian-recorder/commit/3a55c1783573b62bd495ea665bc571fbd3d7cb8b use it like {code} @Test @ReportMessage("This test should be executed manually too") public void throwExceptionTest() { Assert.assertTrue(true); } {code} It will be added to the method report properties when non-empty. > Add annotation to add comments to test report > --------------------------------------------- > > Key: ARQ-1703 > URL: https://issues.jboss.org/browse/ARQ-1703 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part. > So it would be good if for example we could annotate test method with an annotation like: > @Report("This test should be executed manually too") > And then this message may be available on reporter class and could be written to report. -- 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 From issues at jboss.org Tue Mar 11 10:34:05 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 10:34:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1703) Add annotation to add comments to test report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1703. ------------------------------------ Assignee: Stefan Miklosovic Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Add annotation to add comments to test report > --------------------------------------------- > > Key: ARQ-1703 > URL: https://issues.jboss.org/browse/ARQ-1703 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > Sometimes when you write some automatic tests, you also want that QA team execute them manually, maybe because that business case is critical or because automatic test can only cover one part. > So it would be good if for example we could annotate test method with an annotation like: > @Report("This test should be executed manually too") > And then this message may be available on reporter class and could be written to report. -- 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 From issues at jboss.org Tue Mar 11 10:45:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:45:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-423: ------------------------------- Status: Open (was: Pull Request Sent) Rejecting this pull request, as new one will be created against different branch > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Tue Mar 11 10:45:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:45:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-423: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/99 (was: https://github.com/arquillian/arquillian-graphene/pull/95) Linking a new PR, with all fixes according to [~lfryc] comments. > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Tue Mar 11 10:47:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 11 Mar 2014 10:47:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-423: ------------------------------- Assignee: (was: Juraj H?ska) > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Tue Mar 11 10:55:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 10:55:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1702) Add optional label for report title In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952016#comment-12952016 ] Stefan Miklosovic commented on ARQ-1702: ---------------------------------------- in upstream and resolving as done https://github.com/arquillian/arquillian-recorder/commit/adfc54756a6cc18c8528cb15a6fdd9812bb22457 > Add optional label for report title > ----------------------------------- > > Key: ARQ-1702 > URL: https://issues.jboss.org/browse/ARQ-1702 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like: > > Tests results under ${env} > So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title. -- 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 From issues at jboss.org Tue Mar 11 10:55:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 10:55:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1702) Add optional label for report title In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1702: -------------------------------------- Assignee: Stefan Miklosovic > Add optional label for report title > ----------------------------------- > > Key: ARQ-1702 > URL: https://issues.jboss.org/browse/ARQ-1702 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like: > > Tests results under ${env} > So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title. -- 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 From issues at jboss.org Tue Mar 11 10:55:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 11 Mar 2014 10:55:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1702) Add optional label for report title In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1702. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done > Add optional label for report title > ----------------------------------- > > Key: ARQ-1702 > URL: https://issues.jboss.org/browse/ARQ-1702 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > By default report title is fixed in xslt template or in AsciiDoc document. Allow users to define its own title may open the door to do something like: > > Tests results under ${env} > So the title can be for example "Test results under PRE environment", "Test results under QA environment", and so on, instead of fixed title. -- 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 From issues at jboss.org Tue Mar 11 12:01:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:01:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp: response payload was never registered when used with OCPsoft Rewrite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Description: *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. Warp tests work as long as I use the original unaliased URLs. Warp tests using the aliased URLs fail with {quote} ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered {quote} I created a demonstration project, see README.md for details: https://github.com/albers/arquillian-showcase/tree/rewrite was: I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. Warp tests work as long as I use the original unaliased URLs. Warp tests using the aliased URLs fail with {quote} ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered {quote} I created a demonstration project, see README.md for details: https://github.com/albers/arquillian-showcase/tree/rewrite > Warp: response payload was never registered when used with OCPsoft Rewrite > -------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Tue Mar 11 12:03:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:03:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Summary: Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain (was: Warp: response payload was never registered when used with OCPsoft Rewrite) > Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Tue Mar 11 12:15:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:15:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQ-1489. ----------------------------- Resolution: Done Hey Harald, I have fixed the issue in the master, it should land in Alpha7 soon. > Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Tue Mar 11 12:15:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:15:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQ-1489: ------------------------------- Assignee: Luk?? Fry? > Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Tue Mar 11 12:39:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:39:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: mixes up objects in RequestContext due to wrong use of #hashCode() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Summary: Warp: mixes up objects in RequestContext due to wrong use of #hashCode() (was: Warp: fails execute on WildFly because it mixes up objects in RequestContext) > Warp: mixes up objects in RequestContext due to wrong use of #hashCode() > ------------------------------------------------------------------------ > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Alpha7 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Tue Mar 11 12:39:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:39:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1683) Warp: mixes up objects in RequestContext due to wrong use of HttpServletRequest#hashCode() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1683: ---------------------------- Summary: Warp: mixes up objects in RequestContext due to wrong use of HttpServletRequest#hashCode() (was: Warp: mixes up objects in RequestContext due to wrong use of #hashCode()) > Warp: mixes up objects in RequestContext due to wrong use of HttpServletRequest#hashCode() > ------------------------------------------------------------------------------------------ > > Key: ARQ-1683 > URL: https://issues.jboss.org/browse/ARQ-1683 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha6 > Reporter: Luk?? Fry? > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Alpha7 > > > HttpServletRequest, HttpServletResponse and FilterChain objects are samples of objects stored in RequestContext. > We are getting this exception: > {code} > 20:10:05,423 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/PackedCompressed/DEFAULT/org.richfaces.css/skinning.css: java.lang.IllegalArgumentException: UT010023: Request io.undertow.servlet.spec.HttpServletRequestImpl at 31772f73 was not original or a wrapper > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:117) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > {code} > The problem here is that Warp stores these objects in WarpFilter and it injects them to WarpExecutionObserver where it calls #doFilterChain. > Undertow detects that the objects are mixed up. -- 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 From issues at jboss.org Tue Mar 11 12:39:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:39:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1535) Warp: getting intermittent issues in RichFaces tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1535: ---------------------------- Fix Version/s: (was: warp_1.0.0.Alpha7) > Warp: getting intermittent issues in RichFaces tests > ---------------------------------------------------- > > Key: ARQ-1535 > URL: https://issues.jboss.org/browse/ARQ-1535 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > > See RF-13222 for issue details. -- 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 From issues at jboss.org Tue Mar 11 12:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:41:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in Forward filter chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Summary: Warp Filter: prepend to all other filters in a chain & do not participate in Forward filter chain (was: Warp Filter: needs to be a first filter in a chain and should not participate in Forward filter chain) > Warp Filter: prepend to all other filters in a chain & do not participate in Forward filter chain > ------------------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Tue Mar 11 12:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 11 Mar 2014 12:41:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in forwarding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Summary: Warp Filter: prepend to all other filters in a chain & do not participate in forwarding (was: Warp Filter: prepend to all other filters in a chain & do not participate in Forward filter chain) > Warp Filter: prepend to all other filters in a chain & do not participate in forwarding > --------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Wed Mar 12 04:43:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 04:43:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-426) Provide API for dynamic @Location In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-426: ---------------------------------- Summary: Provide API for dynamic @Location Key: ARQGRA-426 URL: https://issues.jboss.org/browse/ARQGRA-426 Project: Arquillian Graphene Issue Type: Feature Request Components: core Affects Versions: 2.0.1.Final Reporter: Juraj H?ska There are use cases when the same page object has different URLs. One of such use cases is described in [this|] post. To enhance re-usability, we should IMHO provide an API for dynamic @Location resolutions. -- 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 From issues at jboss.org Wed Mar 12 04:45:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 04:45:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-426) Provide API for dynamic @Location In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-426: ------------------------------- Description: There are use cases when the same page object has different URLs. One of such use cases is described in [this|https://community.jboss.org/message/861996#861996] post. To enhance re-usability, we should IMHO provide an API for dynamic @Location resolutions. was: There are use cases when the same page object has different URLs. One of such use cases is described in [this|] post. To enhance re-usability, we should IMHO provide an API for dynamic @Location resolutions. > Provide API for dynamic @Location > --------------------------------- > > Key: ARQGRA-426 > URL: https://issues.jboss.org/browse/ARQGRA-426 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > There are use cases when the same page object has different URLs. One of such use cases is described in [this|https://community.jboss.org/message/861996#861996] post. > To enhance re-usability, we should IMHO provide an API for dynamic @Location resolutions. -- 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 From issues at jboss.org Wed Mar 12 04:55:10 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Mar 2014 04:55:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952186#comment-12952186 ] Alex Soto commented on ARQ-1701: -------------------------------- I have been doing some research about this topic. In case of images it is relatively simple, we can do it natively(http://stackoverflow.com/questions/244164/resize-an-image-in-java-any-open-source-library/244177#244177) or by using an API (http://www.thebuzzmedia.com/software/imgscalr-java-image-scaling-library/) I think that using an API will be better because it deals with some problems of resizing, but if you this could be a problem then I implement with Java 2D natively. The problem is with video resizing, I have only found one library to do it http://www.xuggle.com/xuggler/ but you need to install a software externally because it depends on ffmpeg (works in all OS anyway), so I think that resizing video it is a more complicated that simply calling an API. [~smikloso] Do you have any experience on video management? > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Wed Mar 12 06:17:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 12 Mar 2014 06:17:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952224#comment-12952224 ] Stefan Miklosovic commented on ARQ-1701: ---------------------------------------- xuggler is what we use in desktop recorder implementation of video api, there are yet unreleased implementations here (1). Desktop video recorder will have its own repo, Droidium screenshooter will be part of Droidium alpha5 and browser screenshooter will be part of Graphene project. When you talked about resizing, I was thinking that an image will be resized only from presentation point of view. That means an image would be unmodified as such but it would be "resized" in output HTML page when you set "width" and "hight" attributes to img tag. You would just displayed them differently but they would be just the same as they were. Implementing this would mean you would hack that xsl template around to be able to resize them, from html / xsl point of view, dynamically. (1) https://github.com/smiklosovic/recorder-implementations > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Wed Mar 12 06:33:10 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 12 Mar 2014 06:33:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1701) Allow possibility to resize screenshots In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952234#comment-12952234 ] Alex Soto commented on ARQ-1701: -------------------------------- Interesting point about resizing, I think you are right I could do it from presentation point of view, only calculating the new resize width/height and set parameters to html. Cool!! much less work to do. > Allow possibility to resize screenshots > --------------------------------------- > > Key: ARQ-1701 > URL: https://issues.jboss.org/browse/ARQ-1701 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Priority: Minor > > When a screenshot is taken, user can decide if image is big enough to be added as link and not as embed image. Another approach that may find users useful is resize the image, so for example with a resize property you can decide that if an image is big enough instead of adding it as a link, resize the image to given percentage/fixed width, and embed inside the document. > In this case we should decide if image is resized and nothing more, or if it is resized and add an option to open the full screen. -- 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 From issues at jboss.org Wed Mar 12 06:57:10 2014 From: issues at jboss.org (Harald Albers (JIRA)) Date: Wed, 12 Mar 2014 06:57:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in forwarding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952249#comment-12952249 ] Harald Albers commented on ARQ-1489: ------------------------------------ As the release was not available yet, I tried a local build of 1.0.0.Alpha7. The issue is resolved in the demonstration project (which I updated) and in my production project. Thanks a lot! > Warp Filter: prepend to all other filters in a chain & do not participate in forwarding > --------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Wed Mar 12 07:25:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 12 Mar 2014 07:25:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in forwarding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1489: ---------------------------- Issue Type: Enhancement (was: Feature Request) > Warp Filter: prepend to all other filters in a chain & do not participate in forwarding > --------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Wed Mar 12 08:31:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 08:31:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-423: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Wed Mar 12 08:33:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 08:33:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952272#comment-12952272 ] Juraj H?ska commented on ARQGRA-423: ------------------------------------ The PR was merged with 2.1.X feature branch. > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Wed Mar 12 08:33:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 08:33:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-423: ------------------------------- Fix Version/s: 2.1-Tracking > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- 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 From issues at jboss.org Wed Mar 12 09:25:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 09:25:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-422: ------------------------------- Steps to Reproduce: # git clone https://github.com/richfaces/richfaces-qa.git # git checkout requestGuardReproducer # cd metamer/ftest # mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage was: # git clone https://github.com/richfaces/richfaces-qa.git # git checkout requestGuardReproducer # mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Wed Mar 12 09:41:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 12 Mar 2014 09:41:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-422: ------------------------------- Steps to Reproduce: # git clone https://github.com/richfaces/richfaces-qa.git # git checkout requestGuardReproducer # mvn clean install -DskipTests -Prelease # cd metamer/ftest # mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage was: # git clone https://github.com/richfaces/richfaces-qa.git # git checkout requestGuardReproducer # cd metamer/ftest # mvn clean verify -P jbossas-managed-7-1 -Dtest=TestRequestGuardWithNotifyMessage > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Thu Mar 13 04:46:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Mar 2014 04:46:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-422: ------------------------------- Environment: RichFaces 5.0.0-SNAPSHOT Arquillian Core 1.1.2.Final Arquillian Drone 1.2.3.Final Arquillian Graphene 2.0.1.Final Selenium 2.39.0 FF 25 && Chrome was: RichFaces 5.0.0-SNAPSHOT Arquillian Core 1.1.2.Final Arquillian Drone 1.2.3.Final Arquillian Graphene 2.0.1.Final Selenium 2.39.0 > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > FF 25 && Chrome > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Thu Mar 13 05:32:11 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 13 Mar 2014 05:32:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-422: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/100 I am linking a PR with fix. > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > FF 25 && Chrome > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Thu Mar 13 07:52:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 07:52:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1704) Implement replacement for AndroidDriver dropped in Selenium 2.40 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1704: -------------------------------------- Summary: Implement replacement for AndroidDriver dropped in Selenium 2.40 Key: ARQ-1704 URL: https://issues.jboss.org/browse/ARQ-1704 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic Drone 1.3.0.Final will depend on Selenium 2.40 where AndroidDriver is dropped hence support is dropped from Drone as well. Implement Android-like driver directly in Droidium as a replacement. -- 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 From issues at jboss.org Thu Mar 13 07:52:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 07:52:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1704) Implement replacement for AndroidDriver dropped in Selenium 2.40 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1704: ----------------------------------- Component/s: Extension - Droidium > Implement replacement for AndroidDriver dropped in Selenium 2.40 > ---------------------------------------------------------------- > > Key: ARQ-1704 > URL: https://issues.jboss.org/browse/ARQ-1704 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > > Drone 1.3.0.Final will depend on Selenium 2.40 where AndroidDriver is dropped hence support is dropped from Drone as well. > Implement Android-like driver directly in Droidium as a replacement. -- 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 From issues at jboss.org Thu Mar 13 07:52:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 07:52:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1704) Implement replacement for AndroidDriver dropped in Selenium 2.40 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1704: -------------------------------------- Assignee: Stefan Miklosovic > Implement replacement for AndroidDriver dropped in Selenium 2.40 > ---------------------------------------------------------------- > > Key: ARQ-1704 > URL: https://issues.jboss.org/browse/ARQ-1704 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > > Drone 1.3.0.Final will depend on Selenium 2.40 where AndroidDriver is dropped hence support is dropped from Drone as well. > Implement Android-like driver directly in Droidium as a replacement. -- 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 From issues at jboss.org Thu Mar 13 08:46:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Mar 2014 08:46:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-422: ------------------------------ Fix Version/s: 2.0.2.Final > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > FF 25 && Chrome > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > Fix For: 2.0.2.Final > > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Thu Mar 13 08:46:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Mar 2014 08:46:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-424: ------------------------------ Fix Version/s: 2.0.2.Final > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > Fix For: 2.0.2.Final > > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 13 08:46:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Mar 2014 08:46:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-424) Graphene is not able to find ParametrizedType deeper in class hierarchy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-424. ------------------------------- Assignee: Petr Mensik Resolution: Done > Graphene is not able to find ParametrizedType deeper in class hierarchy > ----------------------------------------------------------------------- > > Key: ARQGRA-424 > URL: https://issues.jboss.org/browse/ARQGRA-424 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1.Final > Reporter: Petr Mensik > Assignee: Petr Mensik > Fix For: 2.0.2.Final > > > I ran into this bug when I tried to to have class inheritance like this > {code}public class AbstractWebDriverTest

extends Arquillian { } > public class AbstractLanguageTest extends AbstractWebDriverTest { } > > public class TestChangeLanguageWithAllAcounts extends AbstractLanguageTest { } > {code} > Code like this will throw an {{java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.reflect.ParameterizedType}} which is caused by the method {{AbstractSearchContextEnricher#getSuperClassActualTypeArguments}}. Graphene is only looking for generic parameters in the parent class and not in the all classes in the hierarchy, so this line will give you exception in case of above example. > {code}Type[] actualTypeArguemnts = ((ParameterizedType) testCase.getClass().getGenericSuperclass()).getActualTypeArguments();{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 From issues at jboss.org Thu Mar 13 08:48:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 13 Mar 2014 08:48:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-422) Regression in request guard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-422: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Regression in request guard > --------------------------- > > Key: ARQGRA-422 > URL: https://issues.jboss.org/browse/ARQGRA-422 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.1.Final > Environment: RichFaces 5.0.0-SNAPSHOT > Arquillian Core 1.1.2.Final > Arquillian Drone 1.2.3.Final > Arquillian Graphene 2.0.1.Final > Selenium 2.39.0 > FF 25 && Chrome > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Priority: Blocker > Fix For: 2.0.2.Final > > > I have a simple page with two inputs, a submit button and two notify messages (one for each input) - > https://github.com/richfaces/richfaces-qa/blob/requestGuardReproducer/metamer/application/src/main/webapp/components/richNotifyMessage/guardReproducer.xhtml > When you guard ajax request when button is clicked, it fails with timeout: > {code} > org.openqa.selenium.TimeoutException: Timed out after 2 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory$RequestIsDone at 19eda624 > {code} > * when you run test (in Steps to Reproduce) all three tests fail on request guard (guarding Ajax request) > * it doesn't matter how WebElement is obtained (WebDriver.find, \@FindBy or \@Page > * these tests fail only when two validation errors are on page, i.e. when two notifyMessage components are displayed > ** e.g. change value of second input from 888 to 8 in guardReproducer.xhtml and it will work > * worked fine with Graphene 2.0.0.Final -- 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 From issues at jboss.org Thu Mar 13 09:32:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:32:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1659) Update Selenium to 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1659: ----------------------------- Fix Version/s: drone_1.3.0.Final (was: drone_2.0.0.Alpha1) > Update Selenium to 2.40.0 > ------------------------- > > Key: ARQ-1659 > URL: https://issues.jboss.org/browse/ARQ-1659 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update Selenium to support latest browsers. > Note, some of the deprecated items might get dropped (AndroidDriver, iOSDriver). We need a strategy how to handle that. -- 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 From issues at jboss.org Thu Mar 13 09:36:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:36:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1705) Update Core to 1.1.3.Final In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1705: -------------------------------- Summary: Update Core to 1.1.3.Final Key: ARQ-1705 URL: https://issues.jboss.org/browse/ARQ-1705 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Karel Piwko Update to lastest Arquillian Core. -- 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 From issues at jboss.org Thu Mar 13 09:38:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:38:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1705) Update Core to 1.1.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1705: ----------------------------- Fix Version/s: drone_1.3.0.Final > Update Core to 1.1.3.Final > -------------------------- > > Key: ARQ-1705 > URL: https://issues.jboss.org/browse/ARQ-1705 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update to lastest Arquillian Core. -- 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 From issues at jboss.org Thu Mar 13 09:42:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:42:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1705) Update Core to 1.1.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1705. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/9f9ce135c882fe652725a1f3280df5d0c90734f4 > Update Core to 1.1.3.Final > -------------------------- > > Key: ARQ-1705 > URL: https://issues.jboss.org/browse/ARQ-1705 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update to lastest Arquillian Core. -- 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 From issues at jboss.org Thu Mar 13 09:44:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:44:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1659) Update Selenium to 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1659. ------------------------------ Resolution: Done Pushed upstream at https://github.com/arquillian/arquillian-extension-drone/commit/c8ffcc68d27111eb3af53c848796998ea394d290 Android and IPhone driver was removed altogether. If you need Android Support, use Arquillian Droidium project. IPhone testing has no migration path. > Update Selenium to 2.40.0 > ------------------------- > > Key: ARQ-1659 > URL: https://issues.jboss.org/browse/ARQ-1659 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update Selenium to support latest browsers. > Note, some of the deprecated items might get dropped (AndroidDriver, iOSDriver). We need a strategy how to handle that. -- 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 From issues at jboss.org Thu Mar 13 09:44:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 13 Mar 2014 09:44:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1659) Update Selenium to 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1659: -------------------------------- Assignee: Karel Piwko > Update Selenium to 2.40.0 > ------------------------- > > Key: ARQ-1659 > URL: https://issues.jboss.org/browse/ARQ-1659 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update Selenium to support latest browsers. > Note, some of the deprecated items might get dropped (AndroidDriver, iOSDriver). We need a strategy how to handle that. -- 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 From issues at jboss.org Thu Mar 13 10:02:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 10:02:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952704#comment-12952704 ] Stefan Miklosovic commented on ARQGRA-408: ------------------------------------------ [~jhuska] [~lfryc] Do you have any particular requirements how this should be done? I would go for similar style as implemented in that smart url mini extension (1) which was heavily inspired from (2). Talking concretely, it could be like {code} @Location(name = SchemeName.HTTP) // http:// @Location(name = SchemeName.HTTPS) // https:// @Location(name = SchemeName.FILE) // file:// @Location(name = SchemeName.RESOURCE) // resource:// @Location(name = SchemeName.DROIDIUM) // and-activity:// {code} where HTTP would be default. (1) https://github.com/smiklosovic/arquillian-smart-url (2) https://issues.jboss.org/browse/ARQ-1321 > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Thu Mar 13 10:04:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 10:04:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952704#comment-12952704 ] Stefan Miklosovic edited comment on ARQGRA-408 at 3/13/14 10:03 AM: -------------------------------------------------------------------- [~jhuska] [~lfryc] Do you have any particular requirements how this should be done? I would go for similar style as implemented in that smart url mini extension (1) which was heavily inspired from (2). Talking concretely, it could be like {code} @Location(scheme = Scheme.HTTP) // http:// @Location(scheme = Scheme.HTTPS) // https:// @Location(scheme = Scheme.FILE) // file:// @Location(scheme = Scheme.RESOURCE) // resource:// @Location(scheme = Scheme.DROIDIUM) // and-activity:// {code} where HTTP would be default. (1) https://github.com/smiklosovic/arquillian-smart-url (2) https://issues.jboss.org/browse/ARQ-1321 was (Author: smikloso): [~jhuska] [~lfryc] Do you have any particular requirements how this should be done? I would go for similar style as implemented in that smart url mini extension (1) which was heavily inspired from (2). Talking concretely, it could be like {code} @Location(name = SchemeName.HTTP) // http:// @Location(name = SchemeName.HTTPS) // https:// @Location(name = SchemeName.FILE) // file:// @Location(name = SchemeName.RESOURCE) // resource:// @Location(name = SchemeName.DROIDIUM) // and-activity:// {code} where HTTP would be default. (1) https://github.com/smiklosovic/arquillian-smart-url (2) https://issues.jboss.org/browse/ARQ-1321 > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Thu Mar 13 14:38:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 14:38:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/101 > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Thu Mar 13 19:18:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:18:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952845#comment-12952845 ] Stefan Miklosovic commented on ARQGRA-425: ------------------------------------------ I can look into this as I do ARQGRA-408. > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Thu Mar 13 19:18:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:18:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQGRA-425: ---------------------------------------- Assignee: Stefan Miklosovic > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Thu Mar 13 19:18:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:18:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQGRA-408: ---------------------------------------- Assignee: Stefan Miklosovic > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Thu Mar 13 19:24:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:24:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-374) Allow to setup custom URL via arquillian.xml configuration with CustmizableURLResourceProvider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952847#comment-12952847 ] Stefan Miklosovic commented on ARQGRA-374: ------------------------------------------ This is pretty much related to ARQGRA-425, I will do this. > Allow to setup custom URL via arquillian.xml configuration with CustmizableURLResourceProvider > ---------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Fix For: 2.1-Tracking > > > {code:xml} > > > http://localhost:8080/app/ > > > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- 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 From issues at jboss.org Thu Mar 13 19:24:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:24:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-374) Allow to setup custom URL via arquillian.xml configuration with CustmizableURLResourceProvider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQGRA-374: ---------------------------------------- Assignee: Stefan Miklosovic > Allow to setup custom URL via arquillian.xml configuration with CustmizableURLResourceProvider > ---------------------------------------------------------------------------------------------- > > Key: ARQGRA-374 > URL: https://issues.jboss.org/browse/ARQGRA-374 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Luk?? Fry? > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > {code:xml} > > > http://localhost:8080/app/ > > > {code} > The provider will obtain URL from {{URLResourceProvider}} and use it if no other URL is provided. > Configuring this provider should also block deploying application, since its unnecessary. -- 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 From issues at jboss.org Thu Mar 13 19:42:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:42:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-409) Support for Ember.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952848#comment-12952848 ] Stefan Miklosovic commented on ARQGRA-409: ------------------------------------------ [~lfryc] check this https://github.com/ALRubinger/continuous-enterprise-development/blob/master/code/application/application/src/test/java/org/cedj/geekseek/test/functional/arquillian/AngularJSDroneExtension.java#L61 In a book itself: "We also have a custom extension to Drone and Arquillian; we need to ensure that "click" and "navigate" events wait for the loading of async calls before doing their time check." By doing this it just waits until whole page is loaded so everything is ready to be used. I think this should be internal part of Graphene and in configuration you would say you are testing ember.js and this enhancer would be applied automatically, why not ... > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-selenium-to-make-integration-tests-in-browser > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-based-application-for-example-ember-js-with-selenium-2 > I believe that such tools might be handy for angular.js testing as well. -- 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 From issues at jboss.org Thu Mar 13 19:44:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 13 Mar 2014 19:44:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-409) Support for Ember.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952848#comment-12952848 ] Stefan Miklosovic edited comment on ARQGRA-409 at 3/13/14 7:43 PM: ------------------------------------------------------------------- [~lfryc] check this https://github.com/ALRubinger/continuous-enterprise-development/blob/master/code/application/application/src/test/java/org/cedj/geekseek/test/functional/arquillian/AngularJSDroneExtension.java#L61 In a book itself: "We also have a custom extension to Drone and Arquillian; we need to ensure that "click" and "navigate" events wait for the loading of async calls before doing their time check." By doing this it just waits until whole page is loaded so everything is ready to be used. I think this should be internal part of Graphene and in configuration you would say you are testing ember.js and this enhancer would be applied automatically, why not ... This is for Angular however maybe after some investigation you could come with similar solution to ember.js. was (Author: smikloso): [~lfryc] check this https://github.com/ALRubinger/continuous-enterprise-development/blob/master/code/application/application/src/test/java/org/cedj/geekseek/test/functional/arquillian/AngularJSDroneExtension.java#L61 In a book itself: "We also have a custom extension to Drone and Arquillian; we need to ensure that "click" and "navigate" events wait for the loading of async calls before doing their time check." By doing this it just waits until whole page is loaded so everything is ready to be used. I think this should be internal part of Graphene and in configuration you would say you are testing ember.js and this enhancer would be applied automatically, why not ... > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-selenium-to-make-integration-tests-in-browser > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-based-application-for-example-ember-js-with-selenium-2 > I believe that such tools might be handy for angular.js testing as well. -- 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 From issues at jboss.org Thu Mar 13 20:14:10 2014 From: issues at jboss.org (Scott Stark (JIRA)) Date: Thu, 13 Mar 2014 20:14:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1479) NoSuchMethodError with weld se container and junit continer 1.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952850#comment-12952850 ] Scott Stark commented on ARQ-1479: ---------------------------------- I had a similar problem using the arquillian-weld-ee-embedded-1.1 1.0.0.CR8, but the suggested workaround did not work. What I had to do was to exclude the arquillian-container-spi from the arquillian-weld-ee-embedded-1.1 dependency: org.jboss.arquillian.container arquillian-weld-ee-embedded-1.1 1.0.0.CR8 test org.jboss.arquillian.container arquillian-container-spi > NoSuchMethodError with weld se container and junit continer 1.1.1 > ----------------------------------------------------------------- > > Key: ARQ-1479 > URL: https://issues.jboss.org/browse/ARQ-1479 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR7 > Reporter: Shay Matasaro > > when using the weld-se 1.0.0.cr7 container with junit 1.1.1 container an exception is thrown: > java.lang.NoSuchMethodError: org.jboss.arquillian.container.spi.client.deployment.Validate.archiveHasExpectedFileExtension(Lorg/jboss/shrinkwrap/api/Archive;)Z > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.logWarningIfArchiveHasUnexpectedFileExtension(AnnotationDeploymentScenarioGenerator.java:130) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:100) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62) > at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) > 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:94) > 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:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) -- 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 From issues at jboss.org Fri Mar 14 03:08:10 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 14 Mar 2014 03:08:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1479) NoSuchMethodError with weld se container and junit continer 1.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952880#comment-12952880 ] Aslak Knutsen commented on ARQ-1479: ------------------------------------ Using the Arquillian-Bom should fix these types of issues, http://arquillian.org/guides/getting_started/#add_the_arquillian_apis > NoSuchMethodError with weld se container and junit continer 1.1.1 > ----------------------------------------------------------------- > > Key: ARQ-1479 > URL: https://issues.jboss.org/browse/ARQ-1479 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR7 > Reporter: Shay Matasaro > > when using the weld-se 1.0.0.cr7 container with junit 1.1.1 container an exception is thrown: > java.lang.NoSuchMethodError: org.jboss.arquillian.container.spi.client.deployment.Validate.archiveHasExpectedFileExtension(Lorg/jboss/shrinkwrap/api/Archive;)Z > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.logWarningIfArchiveHasUnexpectedFileExtension(AnnotationDeploymentScenarioGenerator.java:130) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:100) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62) > at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) > 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:94) > 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:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) -- 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 From issues at jboss.org Fri Mar 14 03:10:10 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 14 Mar 2014 03:10:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1479) NoSuchMethodError with weld se container and junit continer 1.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1479. -------------------------------- Assignee: Aslak Knutsen Resolution: Rejected > NoSuchMethodError with weld se container and junit continer 1.1.1 > ----------------------------------------------------------------- > > Key: ARQ-1479 > URL: https://issues.jboss.org/browse/ARQ-1479 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR7 > Reporter: Shay Matasaro > Assignee: Aslak Knutsen > > when using the weld-se 1.0.0.cr7 container with junit 1.1.1 container an exception is thrown: > java.lang.NoSuchMethodError: org.jboss.arquillian.container.spi.client.deployment.Validate.archiveHasExpectedFileExtension(Lorg/jboss/shrinkwrap/api/Archive;)Z > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.logWarningIfArchiveHasUnexpectedFileExtension(AnnotationDeploymentScenarioGenerator.java:130) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:100) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62) > at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) > 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:94) > 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:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) -- 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 From issues at jboss.org Fri Mar 14 03:10:10 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Fri, 14 Mar 2014 03:10:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1479) NoSuchMethodError with weld se container and junit continer 1.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1479. ------------------------------ > NoSuchMethodError with weld se container and junit continer 1.1.1 > ----------------------------------------------------------------- > > Key: ARQ-1479 > URL: https://issues.jboss.org/browse/ARQ-1479 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR7 > Reporter: Shay Matasaro > Assignee: Aslak Knutsen > > when using the weld-se 1.0.0.cr7 container with junit 1.1.1 container an exception is thrown: > java.lang.NoSuchMethodError: org.jboss.arquillian.container.spi.client.deployment.Validate.archiveHasExpectedFileExtension(Lorg/jboss/shrinkwrap/api/Archive;)Z > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.logWarningIfArchiveHasUnexpectedFileExtension(AnnotationDeploymentScenarioGenerator.java:130) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:100) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:62) > at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) > 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:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) > 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:94) > 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:75) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) -- 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 From issues at jboss.org Fri Mar 14 04:18:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:18:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-409) Support for Ember.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952896#comment-12952896 ] Luk?? Fry? commented on ARQGRA-409: ----------------------------------- +1 we can do that for both of frameworks, I just don't know Ember.js internals. Angular wraps all XHR objects and timeouts in order to be able run its model/view synchronization process. Ember doesn't have to allow similar mechanism at all. So let's go ahead and research whether there is a way. :-) ---- On side note, for AngularJS, it is very handy to have special selectors based on ng- attributes such as ng-click, ng-model, etc, such as: {code} @FindByNg(model = "username") WebElement usernameInput; @FindByNg(action = "search()") WebElement searchButton; {code} Is there anything similar for Ember? ---- I would love to have extensions for Graphene and certain frameworks in place. so you could just add artifact on classpath and you will be all setup: {code} graphene-ember graphene-angular {code} > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-selenium-to-make-integration-tests-in-browser > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-based-application-for-example-ember-js-with-selenium-2 > I believe that such tools might be handy for angular.js testing as well. -- 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 From issues at jboss.org Fri Mar 14 04:20:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:20:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and callbacks In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-427: --------------------------------- Summary: Support for AngularJS locators and callbacks Key: ARQGRA-427 URL: https://issues.jboss.org/browse/ARQGRA-427 Project: Arquillian Graphene Issue Type: Bug Reporter: Luk?? Fry? -- 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 From issues at jboss.org Fri Mar 14 04:20:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:20:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and interaction syncing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-427: ------------------------------ Summary: Support for AngularJS locators and interaction syncing (was: Support for AngularJS locators and callbacks) > Support for AngularJS locators and interaction syncing > ------------------------------------------------------ > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Luk?? Fry? > -- 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 From issues at jboss.org Fri Mar 14 04:20:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:20:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and interaction synchronization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952897#comment-12952897 ] Luk?? Fry? commented on ARQGRA-427: ----------------------------------- Selectors: {code} @FindByNg(model = "username") WebElement usernameInput; @FindByNg(action = "search()") WebElement searchButton; {code} --- Syncing interaction: https://github.com/ALRubinger/continuous-enterprise-development/blob/master/code/application/application/src/test/java/org/cedj/geekseek/test/functional/arquillian/AngularJSDroneExtension.java#L84 > Support for AngularJS locators and interaction synchronization > -------------------------------------------------------------- > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Luk?? Fry? > -- 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 From issues at jboss.org Fri Mar 14 04:20:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:20:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and interaction synchronization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-427: ------------------------------ Summary: Support for AngularJS locators and interaction synchronization (was: Support for AngularJS locators and interaction syncing) > Support for AngularJS locators and interaction synchronization > -------------------------------------------------------------- > > Key: ARQGRA-427 > URL: https://issues.jboss.org/browse/ARQGRA-427 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Luk?? Fry? > -- 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 From issues at jboss.org Fri Mar 14 04:20:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:20:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-409) Support for Ember.js In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952898#comment-12952898 ] Luk?? Fry? commented on ARQGRA-409: ----------------------------------- Created: ARQGRA-427 > Support for Ember.js > -------------------- > > Key: ARQGRA-409 > URL: https://issues.jboss.org/browse/ARQGRA-409 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.0.Final > Reporter: Karel Piwko > > Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated. > It would be great it Graphene could provide: > * A way how to stability ids for elements in DOM generated as a part of view > * Guards that are able to guard DOM update without any request. > [~smikloso] can provide more details, additional discussions at: > http://stackoverflow.com/questions/12933422/ember-best-practices-with-selenium-to-make-integration-tests-in-browser > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-based-application-for-example-ember-js-with-selenium-2 > I believe that such tools might be handy for angular.js testing as well. -- 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 From issues at jboss.org Fri Mar 14 04:38:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:38:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952906#comment-12952906 ] Luk?? Fry? commented on ARQGRA-408: ----------------------------------- Sounds good. 1) Wouldn't Droidium users appreciate that they won't need to configure scheme on each location? I.e. they should be able to configure scheme globally: {code} org.jboss.arquillian.graphene.location.Scheme.HTTPS {code} 2) Shouldn't we make Scheme an extensible concept? As you said, having extensible set of schemes {HTTP,HTTPS,FILE,RESOURCE} that could e.g. Droidium extend with Scheme.DROIDIUM. There should be SPI for registration new schemes. Wdyt? > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Fri Mar 14 04:40:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:40:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-425) Allow @Location with relative URL when there is no deployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952910#comment-12952910 ] Luk?? Fry? commented on ARQGRA-425: ----------------------------------- This is duplicate of ARQGRA-374. > Allow @Location with relative URL when there is no deployment > ------------------------------------------------------------- > > Key: ARQGRA-425 > URL: https://issues.jboss.org/browse/ARQGRA-425 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj H?ska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > There are some use cases when there is no {{@Deployment}} method, and we still need to treat {{URL}} in {{@Location}} as relative. > E.g. we are testing an application already deployed somewhere, but still the context root of the application can change, and we do not want to hardcode it. > As [~kpiwko] suggested, we can support his in Graphene like this: > # wrap {{org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider}} > # make it returns some default value of {{contextRoot}} if the {{contextRoot}} is null > # make that value configurable via Graphene configuration -- 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 From issues at jboss.org Fri Mar 14 04:44:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:44:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-428) Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-428: --------------------------------- Summary: Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 Key: ARQGRA-428 URL: https://issues.jboss.org/browse/ARQGRA-428 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Luk?? Fry? -- 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 From issues at jboss.org Fri Mar 14 04:44:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 04:44:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-428) Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-428: ------------------------------ Fix Version/s: 2.0.2 > Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 > -------------------------------------------- > > Key: ARQGRA-428 > URL: https://issues.jboss.org/browse/ARQGRA-428 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Fix For: 2.0.2 > > -- 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 From issues at jboss.org Fri Mar 14 04:44:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 14 Mar 2014 04:44:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12952913#comment-12952913 ] Stefan Miklosovic commented on ARQGRA-408: ------------------------------------------ 1) +1 2) I do not know how to do it. When it comes to it, you use that UriScheme enumeration in Location annotation. When you want to use anothe scheme, I just do not see a way how to add there your custom one without changing UriScheme enumeration. Maybe UriScheme would implement some base interface so you would implement your own as well or your custom scheme would extends base UriScheme. I am not sure. Wdty? :) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Fri Mar 14 09:40:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 14 Mar 2014 09:40:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953045#comment-12953045 ] Luk?? Fry? commented on ARQGRA-408: ----------------------------------- 2) I usually use just a final class with constant immutable members: https://github.com/arquillian/arquillian-graphene/blob/1.0.0.Final/graphene-selenium/graphene-selenium-api/src/main/java/org/jboss/arquillian/ajocado/dom/Attribute.java#L39 > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Fri Mar 14 09:42:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 14 Mar 2014 09:42:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1673) Implement asciidoctor exporter for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1673: ----------------------------------- Assignee: Alex Soto > Implement asciidoctor exporter for reporter > ------------------------------------------- > > Key: ARQ-1673 > URL: https://issues.jboss.org/browse/ARQ-1673 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Alex Soto > -- 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 From issues at jboss.org Fri Mar 14 09:44:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 14 Mar 2014 09:44:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1673) Implement asciidoctor exporter for reporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1673. ------------------------------------ Fix Version/s: recorder_1.0.0.Alpha2 Resolution: Done https://github.com/arquillian/arquillian-recorder/commit/988e0bfbd0bec07536e910b67a11ec7ebccd5b0b > Implement asciidoctor exporter for reporter > ------------------------------------------- > > Key: ARQ-1673 > URL: https://issues.jboss.org/browse/ARQ-1673 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Alex Soto > Fix For: recorder_1.0.0.Alpha2 > > -- 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 From issues at jboss.org Fri Mar 14 11:24:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 14 Mar 2014 11:24:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953148#comment-12953148 ] Stefan Miklosovic commented on ARQGRA-408: ------------------------------------------ [~lfryc] when you meant it like this {code} @Location(scheme = UriScheme.HTTP) {code} where UriScheme is {code} public class UriScheme { public static final UriScheme HTTP = new UriScheme("http"); private final String scheme; private UriScheme(String scheme) { this.scheme = scheme; } } {code} you can not have that class as a parameter for an annotation just because of Java. I try to approach that with enumerations again. > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Sat Mar 15 12:42:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 12:42:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1659) Update Selenium to 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1659. ---------------------------- > Update Selenium to 2.40.0 > ------------------------- > > Key: ARQ-1659 > URL: https://issues.jboss.org/browse/ARQ-1659 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update Selenium to support latest browsers. > Note, some of the deprecated items might get dropped (AndroidDriver, iOSDriver). We need a strategy how to handle that. -- 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 From issues at jboss.org Sat Mar 15 12:42:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 12:42:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1705) Update Core to 1.1.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1705. ---------------------------- > Update Core to 1.1.3.Final > -------------------------- > > Key: ARQ-1705 > URL: https://issues.jboss.org/browse/ARQ-1705 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.0.Final > > > Update to lastest Arquillian Core. -- 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 From issues at jboss.org Sat Mar 15 14:48:10 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Sat, 15 Mar 2014 14:48:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: Alex Soto created ARQ-1706: ------------------------------ Summary: Add multilanguage to AsciiDocExporter Key: ARQ-1706 URL: https://issues.jboss.org/browse/ARQ-1706 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Alex Soto Priority: Minor Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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 From issues at jboss.org Sat Mar 15 15:40:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 15:40:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1707) Provide better timeout exception message In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1707: -------------------------------- Summary: Provide better timeout exception message Key: ARQ-1707 URL: https://issues.jboss.org/browse/ARQ-1707 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_2.0.0.Alpha1 In case that Callable instantiation times out, Drone should emit a better message. -- 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 From issues at jboss.org Sat Mar 15 15:54:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 15:54:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-437) Introduce annotation to control lifecycle of selenium session In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-437: ---------------------------- Fix Version/s: drone_2.0.0.Alpha3 (was: drone_2.0.0.Alpha1) > Introduce annotation to control lifecycle of selenium session > ------------------------------------------------------------- > > Key: ARQ-437 > URL: https://issues.jboss.org/browse/ARQ-437 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Luk?? Fry? > Fix For: drone_2.0.0.Alpha3 > > > Following options are being considered: > BEFORE_SUITE > BEFORE_CLASS > BEFORE_METHOD -- 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 From issues at jboss.org Sat Mar 15 17:00:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:00:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1708) Remove legacy configuration In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1708: -------------------------------- Summary: Remove legacy configuration Key: ARQ-1708 URL: https://issues.jboss.org/browse/ARQ-1708 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.3.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Fix For: drone_2.0.0.Alpha1 Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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 From issues at jboss.org Sat Mar 15 17:06:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:06:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1700) Provide Deployment scope support for Drone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1700. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/48d3c38d1829e5b1c8f8229d599ac424feb2939e > Provide Deployment scope support for Drone > ------------------------------------------ > > Key: ARQ-1700 > URL: https://issues.jboss.org/browse/ARQ-1700 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Tadeas Kriz > Fix For: drone_2.0.0.Alpha1 > > > For Droidium and iOSium containers, there should be a support for @Deployment based scopes. > This is a foundation for Drone 2.0.0. -- 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 From issues at jboss.org Sat Mar 15 17:06:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:06:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1707) Provide better timeout exception message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1707. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/e070731df1856e15a5ddeae8882e28b560efd5e7 > Provide better timeout exception message > ---------------------------------------- > > Key: ARQ-1707 > URL: https://issues.jboss.org/browse/ARQ-1707 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > In case that Callable instantiation times out, Drone should emit a better message. -- 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 From issues at jboss.org Sat Mar 15 17:06:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:06:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1688) Drop Selenium 1.0 support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1688. ------------------------------ Assignee: Karel Piwko Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/56701bdceb5bff1e39aae274064ebb631469df97 > Drop Selenium 1.0 support > ------------------------- > > Key: ARQ-1688 > URL: https://issues.jboss.org/browse/ARQ-1688 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Drop Selenium 1.0 altogether from Drone. -- 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 From issues at jboss.org Sat Mar 15 17:06:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:06:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1708) Remove legacy configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1708: ----------------------------- Affects Version/s: (was: drone_1.3.0.Final) > Remove legacy configuration > --------------------------- > > Key: ARQ-1708 > URL: https://issues.jboss.org/browse/ARQ-1708 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. > Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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 From issues at jboss.org Sat Mar 15 17:08:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Sat, 15 Mar 2014 17:08:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1708) Remove legacy configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1708. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/ddf2ea5965068f5e65fc0229f4dc981d7825e560 > Remove legacy configuration > --------------------------- > > Key: ARQ-1708 > URL: https://issues.jboss.org/browse/ARQ-1708 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove system property based configuration provided by Drone, as this is now available in Arquillian Core. > Remove configuration fields mapped as deprecated, that are now mapped to capabilities. -- 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 From issues at jboss.org Sat Mar 15 18:22:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 15 Mar 2014 18:22:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/102 (was: https://github.com/arquillian/arquillian-graphene/pull/101) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Sat Mar 15 18:52:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 15 Mar 2014 18:52:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Comment: was deleted (was: [~lfryc] when you meant it like this {code} @Location(scheme = UriScheme.HTTP) {code} where UriScheme is {code} public class UriScheme { public static final UriScheme HTTP = new UriScheme("http"); private final String scheme; private UriScheme(String scheme) { this.scheme = scheme; } } {code} you can not have that class as a parameter for an annotation just because of Java. I try to approach that with enumerations again.) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Sat Mar 15 21:34:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sat, 15 Mar 2014 21:34:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQGRA-408: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/103 (was: https://github.com/arquillian/arquillian-graphene/pull/102) > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Mon Mar 17 10:40:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 17 Mar 2014 10:40:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953543#comment-12953543 ] Luk?? Fry? commented on ARQGRA-408: ----------------------------------- Yeah, right, one of other approaches could be using marking interface for an enumeration of classes: http://deltaspike.apache.org/jsf.html#view > Provide SPI for custom @Location resolution > ------------------------------------------- > > Key: ARQGRA-408 > URL: https://issues.jboss.org/browse/ARQGRA-408 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: 2.1-Tracking > > > While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well. > Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things. > The problem is that an activity is started differently, to be concrete, I need to call something like > {code} > browser.get("and-activity://activityName"); > {code} > and I need to do some internal matching of activities to WebDrivers. > To be concrete, follow the link (3). > From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs. > (1) > https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/AeroGearTestCase.java#L140 > (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidium-scenario/src/test/java/org/arquillian/droidium/openblend/fragment/mobile/LoginMobileFragment.java > (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-native/arquillian-droidium-native-impl/src/main/java/org/arquillian/droidium/native_/activity/NativeActivityManager.java#L46 -- 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 From issues at jboss.org Mon Mar 17 11:14:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 17 Mar 2014 11:14:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 In-Reply-To: References: Message-ID: Karel Piwko created ARQGRA-429: ---------------------------------- Summary: Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 Key: ARQGRA-429 URL: https://issues.jboss.org/browse/ARQGRA-429 Project: Arquillian Graphene Issue Type: Bug Reporter: Karel Piwko Priority: Blocker Due to missing AndroidDriver, this fails https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java {code} java.lang.IllegalStateException: Can't invoke method sendKeys. at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) 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:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) 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) Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) ... 87 more Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 115 more {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 From issues at jboss.org Mon Mar 17 11:14:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 17 Mar 2014 11:14:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQGRA-429: ------------------------------- Affects Version/s: 2.0.1 > Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 > ------------------------------------------------------------------------- > > Key: ARQGRA-429 > URL: https://issues.jboss.org/browse/ARQGRA-429 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Karel Piwko > Priority: Blocker > > Due to missing AndroidDriver, this fails > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java > {code} > > java.lang.IllegalStateException: Can't invoke method sendKeys. > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) > at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver > at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) > at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) > at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) > at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) > at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) > at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > ... 87 more > Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 115 more > {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 From issues at jboss.org Mon Mar 17 11:16:11 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 17 Mar 2014 11:16:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQGRA-429: --------------------------------- Fix Version/s: 2.0.2 > Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 > ------------------------------------------------------------------------- > > Key: ARQGRA-429 > URL: https://issues.jboss.org/browse/ARQGRA-429 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Karel Piwko > Priority: Blocker > Fix For: 2.0.2 > > > Due to missing AndroidDriver, this fails > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java > {code} > > java.lang.IllegalStateException: Can't invoke method sendKeys. > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) > at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver > at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) > at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) > at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) > at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) > at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) > at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > ... 87 more > Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 115 more > {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 From issues at jboss.org Mon Mar 17 11:46:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 17 Mar 2014 11:46:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1709) Remove redundant configuration property baseDir In-Reply-To: References: Message-ID: Juraj H?ska created ARQ-1709: -------------------------------- Summary: Remove redundant configuration property baseDir Key: ARQ-1709 URL: https://issues.jboss.org/browse/ARQ-1709 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha2 Reporter: Juraj H?ska Priority: Minor {{baseDir}} is IMHO a redundant configuration property. It is always a part of the {{rootDir}} property, so we can denote the final folder for screenshots by that property. IMO, removing it will make configuration more concise and clear. -- 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 From issues at jboss.org Mon Mar 17 11:52:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 11:52:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1710: -------------------------------------- Summary: Integrate desktop video recorder project to recorder extension Key: ARQ-1710 URL: https://issues.jboss.org/browse/ARQ-1710 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Mon Mar 17 12:28:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 17 Mar 2014 12:28:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-429: ------------------------------ Summary: Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency (was: Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0) > Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency > ------------------------------------------------------------------------------------------------- > > Key: ARQGRA-429 > URL: https://issues.jboss.org/browse/ARQGRA-429 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Karel Piwko > Priority: Blocker > Fix For: 2.0.2 > > > Due to missing AndroidDriver, this fails > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java > {code} > > java.lang.IllegalStateException: Can't invoke method sendKeys. > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) > at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver > at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) > at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) > at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) > at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) > at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) > at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > ... 87 more > Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 115 more > {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 From issues at jboss.org Mon Mar 17 12:30:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 17 Mar 2014 12:30:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQGRA-429: ------------------------------ Description: Was: Summary: Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 Due to missing AndroidDriver, this fails https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java {code} java.lang.IllegalStateException: Can't invoke method sendKeys. at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) 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:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) 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) Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) ... 87 more Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 115 more {code} was: Due to missing AndroidDriver, this fails https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java {code} java.lang.IllegalStateException: Can't invoke method sendKeys. at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) 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:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) 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) Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) ... 87 more Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 115 more {code} > Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency > ------------------------------------------------------------------------------------------------- > > Key: ARQGRA-429 > URL: https://issues.jboss.org/browse/ARQGRA-429 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Karel Piwko > Priority: Blocker > Fix For: 2.0.2 > > > Was: Summary: Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 > Due to missing AndroidDriver, this fails > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java > {code} > > java.lang.IllegalStateException: Can't invoke method sendKeys. > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) > at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver > at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) > at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) > at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) > at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) > at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) > at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > ... 87 more > Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 115 more > {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 From issues at jboss.org Mon Mar 17 12:34:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:34:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1709) Remove redundant configuration property baseDir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1709: ----------------------------------- Affects Version/s: recorder_1.0.0.Alpha1 (was: recorder_1.0.0.Alpha2) > Remove redundant configuration property baseDir > ----------------------------------------------- > > Key: ARQ-1709 > URL: https://issues.jboss.org/browse/ARQ-1709 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > > {{baseDir}} is IMHO a redundant configuration property. > It is always a part of the {{rootDir}} property, so we can denote the final folder for screenshots by that property. > IMO, removing it will make configuration more concise and clear. -- 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 From issues at jboss.org Mon Mar 17 12:34:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:34:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1709) Remove redundant configuration property baseDir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1709: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > Remove redundant configuration property baseDir > ----------------------------------------------- > > Key: ARQ-1709 > URL: https://issues.jboss.org/browse/ARQ-1709 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > {{baseDir}} is IMHO a redundant configuration property. > It is always a part of the {{rootDir}} property, so we can denote the final folder for screenshots by that property. > IMO, removing it will make configuration more concise and clear. -- 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 From issues at jboss.org Mon Mar 17 12:34:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:34:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1709) Remove redundant configuration property baseDir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1709: -------------------------------------- Assignee: Stefan Miklosovic > Remove redundant configuration property baseDir > ----------------------------------------------- > > Key: ARQ-1709 > URL: https://issues.jboss.org/browse/ARQ-1709 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > {{baseDir}} is IMHO a redundant configuration property. > It is always a part of the {{rootDir}} property, so we can denote the final folder for screenshots by that property. > IMO, removing it will make configuration more concise and clear. -- 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 From issues at jboss.org Mon Mar 17 12:34:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:34:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1709) Remove redundant configuration property baseDir In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1709. ------------------------------------ Resolution: Done https://github.com/arquillian/arquillian-recorder/commit/5e101860c3567f3add0b51a730c1396a743f359a > Remove redundant configuration property baseDir > ----------------------------------------------- > > Key: ARQ-1709 > URL: https://issues.jboss.org/browse/ARQ-1709 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha2 > > > {{baseDir}} is IMHO a redundant configuration property. > It is always a part of the {{rootDir}} property, so we can denote the final folder for screenshots by that property. > IMO, removing it will make configuration more concise and clear. -- 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 From issues at jboss.org Mon Mar 17 12:36:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:36:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1710: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha2 > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > -- 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 From issues at jboss.org Mon Mar 17 12:36:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 17 Mar 2014 12:36:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1710. ------------------------------------ Assignee: Stefan Miklosovic Resolution: Done https://github.com/arquillian/arquillian-recorder/commit/2ec62f09f1ed2f15f1a75d0da2530b1cc4424f65 > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > -- 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 From issues at jboss.org Mon Mar 17 12:40:11 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 17 Mar 2014 12:40:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-429) Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-429. ------------------------------- Assignee: Luk?? Fry? Resolution: Done > Graphene should not use selenium-bom (inherited from Drone) + get rid of AndroidDriver dependency > ------------------------------------------------------------------------------------------------- > > Key: ARQGRA-429 > URL: https://issues.jboss.org/browse/ARQGRA-429 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Karel Piwko > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 2.0.2 > > > Was: Summary: Graphene JavaScript excecution is broken with Drone 1.3.0/Selenium 2.40.0 > Due to missing AndroidDriver, this fails > https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/javascript/JavaScriptUtils.java > {code} > > java.lang.IllegalStateException: Can't invoke method sendKeys. > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:214) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy26.sendKeys(Unknown Source) > at se.iteration.integration.IntegrationTests.basicTest(IntegrationTests.java:105) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > 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) > Caused by: java.lang.NoClassDefFoundError: org/openqa/selenium/android/AndroidDriver > at org.jboss.arquillian.graphene.javascript.JavaScriptUtils.execute(JavaScriptUtils.java:42) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.executeScriptForCall(DefaultExecutionResolver.java:139) > at org.jboss.arquillian.graphene.javascript.DefaultExecutionResolver.execute(DefaultExecutionResolver.java:78) > at org.jboss.arquillian.graphene.javascript.JSInterfaceHandler.intercept(JSInterfaceHandler.java:58) > at org.jboss.arquillian.graphene.cglib.ClassImposterizer$ClassWithSuperclassToWorkAroundCglibBug$$EnhancerByGraphene$$29b1f8c.findElements() > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElements(ByJQueryImpl.java:65) > at org.jboss.arquillian.graphene.findby.ByJQueryImpl.findElement(ByJQueryImpl.java:80) > at org.jboss.arquillian.graphene.findby.ByJQuery.findElement(ByJQuery.java:72) > at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318) > at org.jboss.arquillian.graphene.enricher.WebElementUtils.dropProxyAndFindElement(WebElementUtils.java:156) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$5.getTarget(WebElementUtils.java:122) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:186) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > ... 87 more > Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.android.AndroidDriver > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 115 more > {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 From issues at jboss.org Tue Mar 18 13:46:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 18 Mar 2014 13:46:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1711) Unclear message if activity is not found In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1711: -------------------------------- Summary: Unclear message if activity is not found Key: ARQ-1711 URL: https://issues.jboss.org/browse/ARQ-1711 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Karel Piwko If I try to select not existing activity, there should be a better message. It should rather say that activity was not found, not that webdriver was not found. {code} android.getActivityManagerProvider().getActivityManager().startActivity("com.aerogear.hellopush.HelloPush"); driver.switchTo().window("WEBVIEW"); {code} {code} aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase) Time elapsed: 7.146 sec <<< ERROR! org.arquillian.droidium.native_.activity.WebDriverInstanceNotFoundException: There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getAsSimpleName(ActivityWebDriverMapper.java:93) at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getInstance(ActivityWebDriverMapper.java:76) at org.arquillian.droidium.native_.activity.NativeActivityManager.startActivity(NativeActivityManager.java:40) at org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase.aerogearPushPluginNotification(AeroGearPushPluginCordovaTestCase.java:82) 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:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) 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:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator INFO: Stopping Android emulator of AVD name 7939b2e1-1127-4bd8-a9af-0da93f7da99e. Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator INFO: Waiting 60 seconds for emulator 7939b2e1-1127-4bd8-a9af-0da93f7da99e to be disconnected and shutdown. Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown stopEmulator INFO: Stopping emulator emulator-5554 via port 5554. ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown waitUntilShutDownIsComplete INFO: Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e on port 5554 was disconnected in 6 seconds. Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidVirtualDeviceManager deleteAndroidVirtualDevice INFO: Android Virtual Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e deleted. Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector terminateAndroidDebugBridge INFO: Disconnecting Android Debug Bridge. Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl disconnect INFO: Disconnecting Android Debug Bridge at /home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/platform-tools/adb Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector afterTerminateAndroidDebugBridge INFO: Executing operations after disconnecting from Android Debug Bridge Results : Tests in error: aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase): There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. {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 From issues at jboss.org Tue Mar 18 14:32:11 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 18 Mar 2014 14:32:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1012) org.junit.Assume API not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1012. -------------------------------- Assignee: Aslak Knutsen Fix Version/s: 1.1.4.Final Resolution: Done > org.junit.Assume API not working > -------------------------------- > > Key: ARQ-1012 > URL: https://issues.jboss.org/browse/ARQ-1012 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Integration Test Suite > Affects Versions: 1.0.0.Final > Environment: Windows 7, Java 1.7 > Reporter: Karsten Ohme > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Hi, > my test classes are annotated with @RunWith(Arquillian.class) > I try to use the newer JUnit org.junit.Assume API. > The problem ist, that the outcome of the test seems to be ignored, e.g. org.junit.Assume.assertNonNull does not fail and throws an exception. -- 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 From issues at jboss.org Tue Mar 18 14:34:10 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 18 Mar 2014 14:34:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1641) Tests with failed assumptions do not show up as skipped In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1641. -------------------------------- Assignee: Aslak Knutsen Fix Version/s: 1.1.4.Final Resolution: Done Resolved by ARQ-1012 > Tests with failed assumptions do not show up as skipped > ------------------------------------------------------- > > Key: ARQ-1641 > URL: https://issues.jboss.org/browse/ARQ-1641 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > A test like this reports success instead of skipped. > Occurs with managed wildfly, tomcat, karaf > {code} > @Test > public void foo() throws Exception { > Assume.assumeTrue(false); > > // test code that should only run when the above is true > } > {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 From issues at jboss.org Wed Mar 19 04:58:10 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 19 Mar 2014 04:58:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-430) Setup continous integration of 2.1 branch In-Reply-To: References: Message-ID: Luk?? Fry? created ARQGRA-430: --------------------------------- Summary: Setup continous integration of 2.1 branch Key: ARQGRA-430 URL: https://issues.jboss.org/browse/ARQGRA-430 Project: Arquillian Graphene Issue Type: Task Reporter: Luk?? Fry? -- 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 From issues at jboss.org Wed Mar 19 09:38:11 2014 From: issues at jboss.org (Harald Albers (JIRA)) Date: Wed, 19 Mar 2014 09:38:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1489) Warp Filter: prepend to all other filters in a chain & do not participate in forwarding In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harald Albers reopened ARQ-1489: -------------------------------- I'm sorry, but the issue seems to be resolved only for builds on Windows (7) machines. Trying to build my demonstration project (and my production project) on Debian 6 or Debian 7 produced the very same error. > Warp Filter: prepend to all other filters in a chain & do not participate in forwarding > --------------------------------------------------------------------------------------- > > Key: ARQ-1489 > URL: https://issues.jboss.org/browse/ARQ-1489 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: 1.0.0.Alpha4 > Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final > Reporter: Harald Albers > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Alpha7 > > > *Original title*: Warp: response payload was never registered when used with OCPsoft Rewrite > I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp. > Warp tests work as long as I use the original unaliased URLs. > Warp tests using the aliased URLs fail with > {quote} > ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered > {quote} > I created a demonstration project, see README.md for details: > https://github.com/albers/arquillian-showcase/tree/rewrite -- 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 From issues at jboss.org Wed Mar 19 10:02:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 19 Mar 2014 10:02:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1712) Support for process identification/timespamp In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1712: -------------------------------- Summary: Support for process identification/timespamp Key: ARQ-1712 URL: https://issues.jboss.org/browse/ARQ-1712 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha1 Reporter: Karel Piwko Spacelift currently always outputs process identification (based on first argument). It should be possible to: * make this string configurable * disable this altogether * add timestamp to the output There should be both API and system property approach - for disabling and timespamps. This will help make logs more readable. -- 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 From issues at jboss.org Wed Mar 19 11:28:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 19 Mar 2014 11:28:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-431) Case insensitive matcher In-Reply-To: References: Message-ID: Karel Piwko created ARQGRA-431: ---------------------------------- Summary: Case insensitive matcher Key: ARQGRA-431 URL: https://issues.jboss.org/browse/ARQGRA-431 Project: Arquillian Graphene Issue Type: Feature Request Components: core Affects Versions: 2.0.1 Reporter: Karel Piwko It is not possible to match text/attribute in case insensitive way. {code} Graphene.waitModel().until().element(notify).text(). {code} * .contains(String) * .equals(String) it should have equalsIgnoreCase as well. A regex matcher would be handy here as well. -- 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 From issues at jboss.org Wed Mar 19 13:26:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 19 Mar 2014 13:26:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1711) Unclear message if activity is not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1711: -------------------------------------- Assignee: Stefan Miklosovic > Unclear message if activity is not found > ---------------------------------------- > > Key: ARQ-1711 > URL: https://issues.jboss.org/browse/ARQ-1711 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > If I try to select not existing activity, there should be a better message. It should rather say that activity was not found, not that webdriver was not found. > {code} > android.getActivityManagerProvider().getActivityManager().startActivity("com.aerogear.hellopush.HelloPush"); > driver.switchTo().window("WEBVIEW"); > {code} > {code} > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase) Time elapsed: 7.146 sec <<< ERROR! > org.arquillian.droidium.native_.activity.WebDriverInstanceNotFoundException: There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getAsSimpleName(ActivityWebDriverMapper.java:93) > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getInstance(ActivityWebDriverMapper.java:76) > at org.arquillian.droidium.native_.activity.NativeActivityManager.startActivity(NativeActivityManager.java:40) > at org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase.aerogearPushPluginNotification(AeroGearPushPluginCordovaTestCase.java:82) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > 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:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Stopping Android emulator of AVD name 7939b2e1-1127-4bd8-a9af-0da93f7da99e. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Waiting 60 seconds for emulator 7939b2e1-1127-4bd8-a9af-0da93f7da99e to be disconnected and shutdown. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown stopEmulator > INFO: Stopping emulator emulator-5554 via port 5554. > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown waitUntilShutDownIsComplete > INFO: Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e on port 5554 was disconnected in 6 seconds. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidVirtualDeviceManager deleteAndroidVirtualDevice > INFO: Android Virtual Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e deleted. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector terminateAndroidDebugBridge > INFO: Disconnecting Android Debug Bridge. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl disconnect > INFO: Disconnecting Android Debug Bridge at /home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/platform-tools/adb > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector afterTerminateAndroidDebugBridge > INFO: Executing operations after disconnecting from Android Debug Bridge > Results : > Tests in error: > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase): There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > {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 From issues at jboss.org Wed Mar 19 15:26:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 19 Mar 2014 15:26:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1711) Unclear message if activity is not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1711: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > Unclear message if activity is not found > ---------------------------------------- > > Key: ARQ-1711 > URL: https://issues.jboss.org/browse/ARQ-1711 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > If I try to select not existing activity, there should be a better message. It should rather say that activity was not found, not that webdriver was not found. > {code} > android.getActivityManagerProvider().getActivityManager().startActivity("com.aerogear.hellopush.HelloPush"); > driver.switchTo().window("WEBVIEW"); > {code} > {code} > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase) Time elapsed: 7.146 sec <<< ERROR! > org.arquillian.droidium.native_.activity.WebDriverInstanceNotFoundException: There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getAsSimpleName(ActivityWebDriverMapper.java:93) > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getInstance(ActivityWebDriverMapper.java:76) > at org.arquillian.droidium.native_.activity.NativeActivityManager.startActivity(NativeActivityManager.java:40) > at org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase.aerogearPushPluginNotification(AeroGearPushPluginCordovaTestCase.java:82) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > 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:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Stopping Android emulator of AVD name 7939b2e1-1127-4bd8-a9af-0da93f7da99e. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Waiting 60 seconds for emulator 7939b2e1-1127-4bd8-a9af-0da93f7da99e to be disconnected and shutdown. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown stopEmulator > INFO: Stopping emulator emulator-5554 via port 5554. > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown waitUntilShutDownIsComplete > INFO: Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e on port 5554 was disconnected in 6 seconds. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidVirtualDeviceManager deleteAndroidVirtualDevice > INFO: Android Virtual Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e deleted. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector terminateAndroidDebugBridge > INFO: Disconnecting Android Debug Bridge. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl disconnect > INFO: Disconnecting Android Debug Bridge at /home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/platform-tools/adb > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector afterTerminateAndroidDebugBridge > INFO: Executing operations after disconnecting from Android Debug Bridge > Results : > Tests in error: > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase): There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > {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 From issues at jboss.org Wed Mar 19 15:28:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 19 Mar 2014 15:28:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1711) Unclear message if activity is not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1711. ------------------------------------ Resolution: Done > Unclear message if activity is not found > ---------------------------------------- > > Key: ARQ-1711 > URL: https://issues.jboss.org/browse/ARQ-1711 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > If I try to select not existing activity, there should be a better message. It should rather say that activity was not found, not that webdriver was not found. > {code} > android.getActivityManagerProvider().getActivityManager().startActivity("com.aerogear.hellopush.HelloPush"); > driver.switchTo().window("WEBVIEW"); > {code} > {code} > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase) Time elapsed: 7.146 sec <<< ERROR! > org.arquillian.droidium.native_.activity.WebDriverInstanceNotFoundException: There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getAsSimpleName(ActivityWebDriverMapper.java:93) > at org.arquillian.droidium.native_.activity.ActivityWebDriverMapper.getInstance(ActivityWebDriverMapper.java:76) > at org.arquillian.droidium.native_.activity.NativeActivityManager.startActivity(NativeActivityManager.java:40) > at org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase.aerogearPushPluginNotification(AeroGearPushPluginCordovaTestCase.java:82) > 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:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > 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:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Stopping Android emulator of AVD name 7939b2e1-1127-4bd8-a9af-0da93f7da99e. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown shutdownEmulator > INFO: Waiting 60 seconds for emulator 7939b2e1-1127-4bd8-a9af-0da93f7da99e to be disconnected and shutdown. > Mar 18, 2014 6:41:37 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown stopEmulator > INFO: Stopping emulator emulator-5554 via port 5554. > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > ERROR (/home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/tools/emulator):error libGL.so: cannot open shared object file: No such file or directory > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidEmulatorShutdown waitUntilShutDownIsComplete > INFO: Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e on port 5554 was disconnected in 6 seconds. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidVirtualDeviceManager deleteAndroidVirtualDevice > INFO: Android Virtual Device 7939b2e1-1127-4bd8-a9af-0da93f7da99e deleted. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector terminateAndroidDebugBridge > INFO: Disconnecting Android Debug Bridge. > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeImpl disconnect > INFO: Disconnecting Android Debug Bridge at /home/kpiwko/devel/mobile/jbossqe-mobile/integration-tests/android-sdk-linux/platform-tools/adb > Mar 18, 2014 6:41:43 PM org.arquillian.droidium.container.impl.AndroidBridgeConnector afterTerminateAndroidDebugBridge > INFO: Executing operations after disconnecting from Android Debug Bridge > Results : > Tests in error: > aerogearPushPluginNotification(org.jboss.aerogearpushplugincordova.test.AeroGearPushPluginCordovaTestCase): There is not any WebDriver instance found for activity of name 'com.aerogear.hellopush.HelloPush'. > {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 From issues at jboss.org Thu Mar 20 04:50:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:50:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1713: -------------------------------- Summary: Not possible to set Google API level Key: ARQ-1713 URL: https://issues.jboss.org/browse/ARQ-1713 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Karel Piwko Priority: Blocker *When*: I want to setup a google API as target, for instance to run VM capable to work with GCM. *Then*: I can use apiLevel property, but this expects only integer and concatenes it with android-. So, it is not possible to set that at all. *Additional information*: We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* So, definitions would look like: * apiLevel=19 => target=android-19 * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Thu Mar 20 04:50:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:50:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1713: ----------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > Not possible to set Google API level > ------------------------------------ > > Key: ARQ-1713 > URL: https://issues.jboss.org/browse/ARQ-1713 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Priority: Blocker > Fix For: droidium_1.0.0.Alpha5 > > > *When*: > I want to setup a google API as target, for instance to run VM capable to work with GCM. > *Then*: > I can use apiLevel property, but this expects only integer and concatenes it with android-. > So, it is not possible to set that at all. > *Additional information*: > We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* > So, definitions would look like: > * apiLevel=19 => target=android-19 > * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Thu Mar 20 04:52:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:52:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1714) Merge release profile to default profile In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1714: -------------------------------- Summary: Merge release profile to default profile Key: ARQ-1714 URL: https://issues.jboss.org/browse/ARQ-1714 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Karel Piwko It does not make sense to have a separate profile -Prelease. Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Thu Mar 20 04:54:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:54:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1715: -------------------------------- Summary: Merge release profile to default profile Key: ARQ-1715 URL: https://issues.jboss.org/browse/ARQ-1715 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Karel Piwko It does not make sense to have a separate profile -Prelease. Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Thu Mar 20 04:54:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:54:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1715: ----------------------------- Affects Version/s: recorder_1.0.0.Alpha1 (was: droidium_1.0.0.Alpha4) > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Thu Mar 20 04:54:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 20 Mar 2014 04:54:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1715: ----------------------------- Component/s: Extension - Recorder (was: Extension - Droidium) > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Thu Mar 20 10:54:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 20 Mar 2014 10:54:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: Juraj H?ska created ARQ-1716: -------------------------------- Summary: Provide support for TestNG Key: ARQ-1716 URL: https://issues.jboss.org/browse/ARQ-1716 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Reporter: Juraj H?ska Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: {code} arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! java.lang.IllegalStateException: Test method is not annotated with @Test annotation at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) 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:606) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.runWorkers(TestRunner.java:1178) at org.testng.TestRunner.privateRun(TestRunner.java:757) at org.testng.TestRunner.run(TestRunner.java:608) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) {code} Its because it is tested only for {{@Test}} from junit package. -- 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 From issues at jboss.org Thu Mar 20 10:56:10 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 20 Mar 2014 10:56:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQ-1716: ----------------------------- Affects Version/s: recorder_1.0.0.Alpha1 > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > 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:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- 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 From issues at jboss.org Thu Mar 20 18:16:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 20 Mar 2014 18:16:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954786#comment-12954786 ] Stefan Miklosovic commented on ARQ-1716: ---------------------------------------- This problem is deeper. Right now, due to impossibility to "return" result from Arquillian class to TestResult I need to check it manually. There is just junit support yet. When I put testng dependency along junit dependency, in order to make that resolution, even in case I have junit test, it treats that test like testng one. It seems, just because of this, there should be two standalone modules for reporter, one which reports junit tests and other which reports testng tests. It seems you just can not mix them together in one artifact. > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > 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:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- 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 From issues at jboss.org Thu Mar 20 18:24:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 20 Mar 2014 18:24:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1713: -------------------------------------- Assignee: Stefan Miklosovic > Not possible to set Google API level > ------------------------------------ > > Key: ARQ-1713 > URL: https://issues.jboss.org/browse/ARQ-1713 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha5 > > > *When*: > I want to setup a google API as target, for instance to run VM capable to work with GCM. > *Then*: > I can use apiLevel property, but this expects only integer and concatenes it with android-. > So, it is not possible to set that at all. > *Additional information*: > We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* > So, definitions would look like: > * apiLevel=19 => target=android-19 > * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Thu Mar 20 18:26:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 20 Mar 2014 18:26:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1714) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1714: -------------------------------------- Assignee: Stefan Miklosovic > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1714 > URL: https://issues.jboss.org/browse/ARQ-1714 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Fri Mar 21 04:54:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 21 Mar 2014 04:54:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1714) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1714: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1714 > URL: https://issues.jboss.org/browse/ARQ-1714 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Fri Mar 21 04:54:11 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 21 Mar 2014 04:54:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1714) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1714. ------------------------------------ Resolution: Done > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1714 > URL: https://issues.jboss.org/browse/ARQ-1714 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Fri Mar 21 05:08:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 05:08:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reopened ARQ-1710: ------------------------------ Reopened, was not released as a part of 1.0.0.Alpha2 > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha2 > > -- 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 From issues at jboss.org Fri Mar 21 05:08:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 05:08:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1710) Integrate desktop video recorder project to recorder extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1710: ----------------------------- Fix Version/s: (was: recorder_1.0.0.Alpha2) > Integrate desktop video recorder project to recorder extension > -------------------------------------------------------------- > > Key: ARQ-1710 > URL: https://issues.jboss.org/browse/ARQ-1710 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- 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 From issues at jboss.org Fri Mar 21 05:10:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 05:10:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1716) Provide support for TestNG In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954862#comment-12954862 ] Karel Piwko commented on ARQ-1716: ---------------------------------- Would it be possible to just bind to Arquillian Events? This is a long term maintenance nightmare - JUnit, TestNG, Cukespace, Spock, etc... > Provide support for TestNG > -------------------------- > > Key: ARQ-1716 > URL: https://issues.jboss.org/browse/ARQ-1716 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Juraj H?ska > > Reporter extension does not work properly with TestNG. For example when test fails with exception, it causes to throw exception by reporter as well: > {code} > arquillianAfterTest(org.richfaces.tests.showcase.ajax.TestAjax) Time elapsed: 5.797 sec <<< FAILURE! > java.lang.IllegalStateException: Test method is not annotated with @Test annotation > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.isThrowingExpectedException(ReporterLifecycleObserver.java:262) > at org.arquillian.recorder.reporter.impl.ReporterLifecycleObserver.observeAfterTest(ReporterLifecycleObserver.java:178) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > 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.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.testng.Arquillian.arquillianAfterTest(Arquillian.java:149) > 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:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:753) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:69) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:120) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:104) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Its because it is tested only for {{@Test}} from junit package. -- 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 From issues at jboss.org Fri Mar 21 05:30:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 05:30:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1717) Update Arquillian BOM to use ShrinkWrap Resolver 2.1.0 In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1717: -------------------------------- Summary: Update Arquillian BOM to use ShrinkWrap Resolver 2.1.0 Key: ARQ-1717 URL: https://issues.jboss.org/browse/ARQ-1717 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.3.Final Reporter: Karel Piwko Update SWR to 2.1.0. This brings support for Maven 3.1.0 and newer. -- 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 From issues at jboss.org Fri Mar 21 07:36:10 2014 From: issues at jboss.org (Tadeas Kriz (JIRA)) Date: Fri, 21 Mar 2014 07:36:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1718) Simple way to test on real device without the need to use serial id In-Reply-To: References: Message-ID: Tadeas Kriz created ARQ-1718: -------------------------------- Summary: Simple way to test on real device without the need to use serial id Key: ARQ-1718 URL: https://issues.jboss.org/browse/ARQ-1718 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Droidium Reporter: Tadeas Kriz There should be a way to simply test on device, without the need to use serial id, if only one device is connected. Adb has this functionality (if only one device (real or emulated) is connected, it uses it, or with -d switch to use real device (-e for emulated one)). Droidium should also allow this and quit with error if no serial id is specified, but more devices are connected. -- 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 From issues at jboss.org Fri Mar 21 08:12:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 08:12:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1719) Command execution failer does not show command In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1719: -------------------------------- Summary: Command execution failer does not show command Key: ARQ-1719 URL: https://issues.jboss.org/browse/ARQ-1719 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha1 Reporter: Karel Piwko If command fails, it shows: {code} Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 23.814 sec <<< FAILURE! - in org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase aerogearCryptoTestSuite(org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase) Time elapsed: 0.046 sec <<< ERROR! org.arquillian.spacelift.process.ProcessExecutionException: Invocation of [Ljava.lang.String;@78c66962 failed with 1 {code} This is useless, it should show real command. -- 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 From issues at jboss.org Fri Mar 21 09:46:10 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 09:46:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1719) Command execution failure does not show command In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1719: ----------------------------- Summary: Command execution failure does not show command (was: Command execution failer does not show command) > Command execution failure does not show command > ----------------------------------------------- > > Key: ARQ-1719 > URL: https://issues.jboss.org/browse/ARQ-1719 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > > If command fails, it shows: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 23.814 sec <<< FAILURE! - in org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase > aerogearCryptoTestSuite(org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase) Time elapsed: 0.046 sec <<< ERROR! > org.arquillian.spacelift.process.ProcessExecutionException: Invocation of [Ljava.lang.String;@78c66962 failed with 1 > {code} > This is useless, it should show real command. -- 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 From issues at jboss.org Fri Mar 21 09:46:11 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Fri, 21 Mar 2014 09:46:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1719) Command execution failure does not show command In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1719. ------------------------------ Assignee: Karel Piwko Fix Version/s: spacelift_1.0.0.Alpha2 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-spacelift/commit/4cbedd583e59c5c34e66afdd516ae74fa89c8338 > Command execution failure does not show command > ----------------------------------------------- > > Key: ARQ-1719 > URL: https://issues.jboss.org/browse/ARQ-1719 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > If command fails, it shows: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 23.814 sec <<< FAILURE! - in org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase > aerogearCryptoTestSuite(org.jboss.aerogearjs.crypto.AeroGearCryptoTestCase) Time elapsed: 0.046 sec <<< ERROR! > org.arquillian.spacelift.process.ProcessExecutionException: Invocation of [Ljava.lang.String;@78c66962 failed with 1 > {code} > This is useless, it should show real command. -- 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 From issues at jboss.org Fri Mar 21 11:44:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 21 Mar 2014 11:44:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1720) Command's toString() method does not take whitespaces into account In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1720: -------------------------------------- Summary: Command's toString() method does not take whitespaces into account Key: ARQ-1720 URL: https://issues.jboss.org/browse/ARQ-1720 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Spacelift Affects Versions: spacelift_1.0.0.Alpha1 Reporter: Stefan Miklosovic In case of invocation of command like this from shell {code} android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t "Google Inc.:Google APIs:17" {code} In order to build that command in Spacelift, having {code} String target = "Google Inc.:Google APIs:17"; {code} this is necessary to do in order to have the same command in Spacelift {code} Command command = new CommandBuilder().add(sdk.getAndroidPath()) .add("create") .add("avd") .add("-n") .add(configuration.getAvdName()) .add("-t") .add(target).build(); {code} However, command.toString() says that Spacelift invoked this {code} android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t Google Inc.:Google APIs:17 {code} But it is not true, in fact, it was executed with enclosing quotes because of present spaces in target string which command.toString() has not taken into account. -- 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 From issues at jboss.org Fri Mar 21 13:26:10 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 21 Mar 2014 13:26:10 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1718) Simple way to test on real device without the need to use serial id In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1718: -------------------------------------- Assignee: Stefan Miklosovic > Simple way to test on real device without the need to use serial id > ------------------------------------------------------------------- > > Key: ARQ-1718 > URL: https://issues.jboss.org/browse/ARQ-1718 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Reporter: Tadeas Kriz > Assignee: Stefan Miklosovic > > There should be a way to simply test on device, without the need to use serial id, if only one device is connected. Adb has this functionality (if only one device (real or emulated) is connected, it uses it, or with -d switch to use real device (-e for emulated one)). Droidium should also allow this and quit with error if no serial id is specified, but more devices are connected. -- 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 From issues at jboss.org Fri Mar 21 17:40:11 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Fri, 21 Mar 2014 17:40:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1624 stopped by Gerhard Poul. > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Fri Mar 21 17:40:11 2014 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Fri, 21 Mar 2014 17:40:11 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12955133#comment-12955133 ] Gerhard Poul commented on ARQ-1624: ----------------------------------- If someone gets a chance to test it, please provide feedback on this issue. tnx! > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > > com.ibm.websphere > ws-admin-client > 8.5.0 > system ${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar > > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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 From issues at jboss.org Mon Mar 24 04:59:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 24 Mar 2014 04:59:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1720) Command's toString() method does not take whitespaces into account In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1720: -------------------------------- Assignee: Karel Piwko > Command's toString() method does not take whitespaces into account > ------------------------------------------------------------------ > > Key: ARQ-1720 > URL: https://issues.jboss.org/browse/ARQ-1720 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Karel Piwko > > In case of invocation of command like this from shell > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t "Google Inc.:Google APIs:17" > {code} > In order to build that command in Spacelift, having > {code} > String target = "Google Inc.:Google APIs:17"; > {code} > this is necessary to do in order to have the same command in Spacelift > {code} > Command command = new CommandBuilder().add(sdk.getAndroidPath()) > .add("create") > .add("avd") > .add("-n") > .add(configuration.getAvdName()) > .add("-t") > .add(target).build(); > {code} > However, command.toString() says that Spacelift invoked this > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t Google Inc.:Google APIs:17 > {code} > But it is not true, in fact, it was executed with enclosing quotes because of present spaces in target string which command.toString() has not taken into account. -- 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 From issues at jboss.org Mon Mar 24 04:59:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 24 Mar 2014 04:59:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1720) Command's toString() method does not take whitespaces into account In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1720: ----------------------------- Fix Version/s: spacelift_1.0.0.Alpha2 > Command's toString() method does not take whitespaces into account > ------------------------------------------------------------------ > > Key: ARQ-1720 > URL: https://issues.jboss.org/browse/ARQ-1720 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > In case of invocation of command like this from shell > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t "Google Inc.:Google APIs:17" > {code} > In order to build that command in Spacelift, having > {code} > String target = "Google Inc.:Google APIs:17"; > {code} > this is necessary to do in order to have the same command in Spacelift > {code} > Command command = new CommandBuilder().add(sdk.getAndroidPath()) > .add("create") > .add("avd") > .add("-n") > .add(configuration.getAvdName()) > .add("-t") > .add(target).build(); > {code} > However, command.toString() says that Spacelift invoked this > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t Google Inc.:Google APIs:17 > {code} > But it is not true, in fact, it was executed with enclosing quotes because of present spaces in target string which command.toString() has not taken into account. -- 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 From issues at jboss.org Mon Mar 24 05:53:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 24 Mar 2014 05:53:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1720) Command's toString() method does not take whitespaces into account In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1720. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-spacelift/commit/2dad9b24d552d671c9fa1a6cfce145db483c0ca1 > Command's toString() method does not take whitespaces into account > ------------------------------------------------------------------ > > Key: ARQ-1720 > URL: https://issues.jboss.org/browse/ARQ-1720 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > In case of invocation of command like this from shell > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t "Google Inc.:Google APIs:17" > {code} > In order to build that command in Spacelift, having > {code} > String target = "Google Inc.:Google APIs:17"; > {code} > this is necessary to do in order to have the same command in Spacelift > {code} > Command command = new CommandBuilder().add(sdk.getAndroidPath()) > .add("create") > .add("avd") > .add("-n") > .add(configuration.getAvdName()) > .add("-t") > .add(target).build(); > {code} > However, command.toString() says that Spacelift invoked this > {code} > android create avd -n fd930b32-69bc-4d52-8313-2c9c27bb4511 -t Google Inc.:Google APIs:17 > {code} > But it is not true, in fact, it was executed with enclosing quotes because of present spaces in target string which command.toString() has not taken into account. -- 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 From issues at jboss.org Mon Mar 24 10:19:14 2014 From: issues at jboss.org (Daniel Smith (JIRA)) Date: Mon, 24 Mar 2014 10:19:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12955641#comment-12955641 ] Daniel Smith commented on ARQ-814: ---------------------------------- I'm in the same boat as [~gulcher] and [~heinz.huber] and would like to get some form of an update. Best I can tell the source of the null value being used in the reflection call is in the call to {{SessionObjectReference.resolveEjb(EjbDescriptor ejbDescriptor)}} as provided by {{MockEjBServices}} > Should support injection of EJBs (as CDI Beans) in Weld Embedded > ---------------------------------------------------------------- > > Key: ARQ-814 > URL: https://issues.jboss.org/browse/ARQ-814 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Anthony O. > Assignee: Marko Luk?a > Attachments: EJBTest.java > > > As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said. > {code} > @RunWith(Arquillian.class) > public class EJBTest { > @Deployment > public static JavaArchive createTestArchive() { > return ShrinkWrap > .create(JavaArchive.class, "test.jar") > .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > } > @Stateless > public static class SomeService { > public String someMethod() { > return "test"; > } > } > @Inject > SomeService someService; > @Test > public void testStatelessCall() { > Assert.assertEquals("test", someService.someMethod()); > } > } > {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 From issues at jboss.org Mon Mar 24 11:31:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 11:31:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1721) Update ddmlib for Droidium to 22.7.1 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1721: -------------------------------------- Summary: Update ddmlib for Droidium to 22.7.1 Key: ARQ-1721 URL: https://issues.jboss.org/browse/ARQ-1721 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: 1.0.0.Alpha4 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Mon Mar 24 11:31:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 11:31:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1721) Update ddmlib for Droidium to 22.7.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1721: ----------------------------------- Affects Version/s: droidium_1.0.0.Alpha4 (was: 1.0.0.Alpha4) > Update ddmlib for Droidium to 22.7.1 > ------------------------------------ > > Key: ARQ-1721 > URL: https://issues.jboss.org/browse/ARQ-1721 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > -- 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 From issues at jboss.org Mon Mar 24 11:31:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 11:31:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1721) Update ddmlib for Droidium to 22.7.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1721: -------------------------------------- Assignee: Stefan Miklosovic > Update ddmlib for Droidium to 22.7.1 > ------------------------------------ > > Key: ARQ-1721 > URL: https://issues.jboss.org/browse/ARQ-1721 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Mon Mar 24 11:31:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 11:31:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1721) Update ddmlib for Droidium to 22.7.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1721: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > Update ddmlib for Droidium to 22.7.1 > ------------------------------------ > > Key: ARQ-1721 > URL: https://issues.jboss.org/browse/ARQ-1721 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Mon Mar 24 11:37:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 11:37:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1721) Update ddmlib for Droidium to 22.7.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1721. ------------------------------------ Resolution: Done > Update ddmlib for Droidium to 22.7.1 > ------------------------------------ > > Key: ARQ-1721 > URL: https://issues.jboss.org/browse/ARQ-1721 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Mon Mar 24 12:05:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 12:05:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1713. ------------------------------------ Resolution: Done > Not possible to set Google API level > ------------------------------------ > > Key: ARQ-1713 > URL: https://issues.jboss.org/browse/ARQ-1713 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha5 > > > *When*: > I want to setup a google API as target, for instance to run VM capable to work with GCM. > *Then*: > I can use apiLevel property, but this expects only integer and concatenes it with android-. > So, it is not possible to set that at all. > *Additional information*: > We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* > So, definitions would look like: > * apiLevel=19 => target=android-19 > * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Mon Mar 24 14:11:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 24 Mar 2014 14:11:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reopened ARQ-1713: ------------------------------------ I am reopening this since in 22.6 there is new system image layout for android-19 up which was not taken into account. However, I am not able to verify it works since this (1) embarrasing bug which prevents user to create AVD from command line. Unless it is repaired in upstream and 22.6.2 will be out, Alpha5 can not go out. (1) https://code.google.com/p/android/issues/detail?id=66819 > Not possible to set Google API level > ------------------------------------ > > Key: ARQ-1713 > URL: https://issues.jboss.org/browse/ARQ-1713 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha5 > > > *When*: > I want to setup a google API as target, for instance to run VM capable to work with GCM. > *Then*: > I can use apiLevel property, but this expects only integer and concatenes it with android-. > So, it is not possible to set that at all. > *Additional information*: > We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* > So, definitions would look like: > * apiLevel=19 => target=android-19 > * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Tue Mar 25 04:45:12 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 25 Mar 2014 04:45:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-428) Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved ARQGRA-428. ------------------------------- Assignee: Luk?? Fry? Resolution: Done > Upgrade Arq Core to 1.1.3 and Drone to 1.3.0 > -------------------------------------------- > > Key: ARQGRA-428 > URL: https://issues.jboss.org/browse/ARQGRA-428 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 2.0.2 > > -- 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 From issues at jboss.org Tue Mar 25 05:46:13 2014 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 25 Mar 2014 05:46:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto reassigned ARQ-1706: ------------------------------ Assignee: Alex Soto > Add multilanguage to AsciiDocExporter > ------------------------------------- > > Key: ARQ-1706 > URL: https://issues.jboss.org/browse/ARQ-1706 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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 From issues at jboss.org Tue Mar 25 06:04:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 06:04:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1722: -------------------------------------- Summary: Name of Screenshooter method setting screenshot type is mangled Key: ARQ-1722 URL: https://issues.jboss.org/browse/ARQ-1722 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: 1.0.0.Alpha2 Reporter: Stefan Miklosovic Priority: Trivial Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- 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 From issues at jboss.org Tue Mar 25 06:06:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 06:06:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1722: -------------------------------------- Assignee: Stefan Miklosovic > Name of Screenshooter method setting screenshot type is mangled > --------------------------------------------------------------- > > Key: ARQ-1722 > URL: https://issues.jboss.org/browse/ARQ-1722 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: 1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > > Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- 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 From issues at jboss.org Tue Mar 25 08:14:12 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 25 Mar 2014 08:14:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1723) Managed Karaf Container should use java instead of bin/karaf In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1723: ----------------------------------- Summary: Managed Karaf Container should use java instead of bin/karaf Key: ARQ-1723 URL: https://issues.jboss.org/browse/ARQ-1723 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final The test client may not have permissions to execute an arbitrary script on the test platform. Using bin/karaf would also not work on windows -- 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 From issues at jboss.org Tue Mar 25 08:14:12 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 25 Mar 2014 08:14:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1724) Managed Karaf Container should use java instead of bin/karaf In-Reply-To: References: Message-ID: Thomas Diesler created ARQ-1724: ----------------------------------- Summary: Managed Karaf Container should use java instead of bin/karaf Key: ARQ-1724 URL: https://issues.jboss.org/browse/ARQ-1724 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final The test client may not have permissions to execute an arbitrary script on the test platform. Using bin/karaf would also not work on windows -- 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 From issues at jboss.org Tue Mar 25 08:32:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Tue, 25 Mar 2014 08:32:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1725) Investigate reporting improvement to complain with IEEE829 In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1725: -------------------------------- Summary: Investigate reporting improvement to complain with IEEE829 Key: ARQ-1725 URL: https://issues.jboss.org/browse/ARQ-1725 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha1 Reporter: Karel Piwko It would be very useful if Reporter allows to add metadata to the report that complies with http://en.wikipedia.org/wiki/IEEE_829 -- 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 From issues at jboss.org Tue Mar 25 09:15:14 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 25 Mar 2014 09:15:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1725) Investigate reporting improvement to compliant with IEEE829 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1725: ------------------------------- Summary: Investigate reporting improvement to compliant with IEEE829 (was: Investigate reporting improvement to complain with IEEE829) > Investigate reporting improvement to compliant with IEEE829 > ----------------------------------------------------------- > > Key: ARQ-1725 > URL: https://issues.jboss.org/browse/ARQ-1725 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It would be very useful if Reporter allows to add metadata to the report that complies with http://en.wikipedia.org/wiki/IEEE_829 -- 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 From issues at jboss.org Tue Mar 25 09:15:14 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Tue, 25 Mar 2014 09:15:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1725) Investigate reporting improvement to be compliant with IEEE829 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen updated ARQ-1725: ------------------------------- Summary: Investigate reporting improvement to be compliant with IEEE829 (was: Investigate reporting improvement to compliant with IEEE829) > Investigate reporting improvement to be compliant with IEEE829 > -------------------------------------------------------------- > > Key: ARQ-1725 > URL: https://issues.jboss.org/browse/ARQ-1725 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > > It would be very useful if Reporter allows to add metadata to the report that complies with http://en.wikipedia.org/wiki/IEEE_829 -- 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 From issues at jboss.org Tue Mar 25 10:49:12 2014 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Tue, 25 Mar 2014 10:49:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1723) Managed Karaf Container should use java instead of bin/karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved ARQ-1723. --------------------------------- Resolution: Done Done in 2.1.0.CR13 > Managed Karaf Container should use java instead of bin/karaf > ------------------------------------------------------------ > > Key: ARQ-1723 > URL: https://issues.jboss.org/browse/ARQ-1723 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: osgi_2.0.0.Final > > > The test client may not have permissions to execute an arbitrary script on the test platform. Using bin/karaf would also not work on windows -- 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 From issues at jboss.org Tue Mar 25 12:13:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 12:13:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1726) Reporter does not consider screenshots taken manually in test methods In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1726: -------------------------------------- Summary: Reporter does not consider screenshots taken manually in test methods Key: ARQ-1726 URL: https://issues.jboss.org/browse/ARQ-1726 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha2 Reporter: Stefan Miklosovic Beside screenshots taken automatically before / after test method according to configuration, user can take screenshots manually with screenshooter injection like this {code} @ArquillianResource Screenshooter screenshooter; public void test() { screenshooter.takeScreenshot(); } {code} It holds for Recoder injection point as well when user can record videos manually in test method like {code} @ArquillianResource Recoder recorder; public void test() { recorder.start(); // something is happening recorder.stop(); } {code} However, these screenshots and videos does not appear in final report file because when it is taken directly by injection interface, it does not fire any screenshot report event. Logic behind screenshooter and recorder knows this because it invokes screenshooter itself but concrete screenshooter implementation does not fire them. There needs to be a way how to report these screenshots which were taken manually as well. Taking of screenshots manually is the "last chance" for a user to take them exactly where he needs them to be taken and not showing them in report could be justified however due to user experience these should be taken into account as well definitely. -- 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 From issues at jboss.org Tue Mar 25 12:51:14 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 12:51:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1671) Integrate screenshooter implementation to Droidium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1671. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha5 Resolution: Done > Integrate screenshooter implementation to Droidium > -------------------------------------------------- > > Key: ARQ-1671 > URL: https://issues.jboss.org/browse/ARQ-1671 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Tue Mar 25 13:09:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:09:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1722: ----------------------------------- Affects Version/s: recorder_1.0.0.Alpha1 (was: 1.0.0.Alpha2) > Name of Screenshooter method setting screenshot type is mangled > --------------------------------------------------------------- > > Key: ARQ-1722 > URL: https://issues.jboss.org/browse/ARQ-1722 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > > Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- 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 From issues at jboss.org Tue Mar 25 13:09:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:09:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1722: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha3 > Name of Screenshooter method setting screenshot type is mangled > --------------------------------------------------------------- > > Key: ARQ-1722 > URL: https://issues.jboss.org/browse/ARQ-1722 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > Fix For: recorder_1.0.0.Alpha3 > > > Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- 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 From issues at jboss.org Tue Mar 25 13:09:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:09:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1722) Name of Screenshooter method setting screenshot type is mangled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1722. ------------------------------------ Resolution: Done > Name of Screenshooter method setting screenshot type is mangled > --------------------------------------------------------------- > > Key: ARQ-1722 > URL: https://issues.jboss.org/browse/ARQ-1722 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > Fix For: recorder_1.0.0.Alpha3 > > > Screenshooter interface has method "setScreensthotType" which is spelled wrongly. -- 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 From issues at jboss.org Tue Mar 25 13:11:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:11:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1715: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha3 > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Fix For: recorder_1.0.0.Alpha3 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Tue Mar 25 13:11:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:11:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1715: -------------------------------------- Assignee: Stefan Miklosovic > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha3 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Tue Mar 25 13:19:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:19:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1715) Merge release profile to default profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1715. ------------------------------------ Resolution: Done moved to build > Merge release profile to default profile > ---------------------------------------- > > Key: ARQ-1715 > URL: https://issues.jboss.org/browse/ARQ-1715 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Fix For: recorder_1.0.0.Alpha3 > > > It does not make sense to have a separate profile -Prelease. > Configuration of release plugin is not triggered by default Maven lifecycle, so activating a profile is unnecessary step. It can be specified directly in -- 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 From issues at jboss.org Tue Mar 25 13:57:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:57:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1706: ----------------------------------- Fix Version/s: recorder_1.0.0.Alpha3 > Add multilanguage to AsciiDocExporter > ------------------------------------- > > Key: ARQ-1706 > URL: https://issues.jboss.org/browse/ARQ-1706 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > Fix For: recorder_1.0.0.Alpha3 > > > Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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 From issues at jboss.org Tue Mar 25 13:57:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:57:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1706: ----------------------------------- Affects Version/s: recorder_1.0.0.Alpha2 > Add multilanguage to AsciiDocExporter > ------------------------------------- > > Key: ARQ-1706 > URL: https://issues.jboss.org/browse/ARQ-1706 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > Fix For: recorder_1.0.0.Alpha3 > > > Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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 From issues at jboss.org Tue Mar 25 13:57:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Tue, 25 Mar 2014 13:57:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1706) Add multilanguage to AsciiDocExporter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1706. ------------------------------------ Resolution: Done Please do not forget to add documentation for it as you mentioned. > Add multilanguage to AsciiDocExporter > ------------------------------------- > > Key: ARQ-1706 > URL: https://issues.jboss.org/browse/ARQ-1706 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > Fix For: recorder_1.0.0.Alpha3 > > > Add multi language to AsciiDocExporter. Currently AsciiDoc document is generated in English. Although Reporter extension allows users to set the language, AsciiDocExporter ignores it. -- 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 From issues at jboss.org Wed Mar 26 09:23:14 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 26 Mar 2014 09:23:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1727) Update to Android SDK 2.22.6 as default supported Android SDK In-Reply-To: References: Message-ID: Karel Piwko created ARQ-1727: -------------------------------- Summary: Update to Android SDK 2.22.6 as default supported Android SDK Key: ARQ-1727 URL: https://issues.jboss.org/browse/ARQ-1727 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: droidium_1.0.0.Alpha5 Update to SDK 2.22.6. Support wearables as well. -- 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 From issues at jboss.org Wed Mar 26 12:23:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Wed, 26 Mar 2014 12:23:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1727) Update to Android SDK 2.22.6 as default supported Android SDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1727: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-droidium/pull/13 > Update to Android SDK 2.22.6 as default supported Android SDK > ------------------------------------------------------------- > > Key: ARQ-1727 > URL: https://issues.jboss.org/browse/ARQ-1727 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: droidium_1.0.0.Alpha5 > > > Update to SDK 2.22.6. Support wearables as well. -- 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 From issues at jboss.org Wed Mar 26 18:50:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 26 Mar 2014 18:50:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1727) Update to Android SDK 22.6.2 as default supported Android SDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1727: ----------------------------------- Summary: Update to Android SDK 22.6.2 as default supported Android SDK (was: Update to Android SDK 2.22.6 as default supported Android SDK) > Update to Android SDK 22.6.2 as default supported Android SDK > ------------------------------------------------------------- > > Key: ARQ-1727 > URL: https://issues.jboss.org/browse/ARQ-1727 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: droidium_1.0.0.Alpha5 > > > Update to SDK 2.22.6. Support wearables as well. -- 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 From issues at jboss.org Wed Mar 26 19:00:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 26 Mar 2014 19:00:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1727) Update to Android SDK 22.6.2 as default supported Android SDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1727: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I added tests on top of that pull request and repaired some minor bugs https://github.com/arquillian/arquillian-droidium/commit/7a4e787c023d716cdf8441fd711060c06679fb4c > Update to Android SDK 22.6.2 as default supported Android SDK > ------------------------------------------------------------- > > Key: ARQ-1727 > URL: https://issues.jboss.org/browse/ARQ-1727 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: droidium_1.0.0.Alpha5 > > > Update to SDK 2.22.6. Support wearables as well. -- 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 From issues at jboss.org Wed Mar 26 19:00:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Wed, 26 Mar 2014 19:00:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1713) Not possible to set Google API level In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1713. ------------------------------------ Resolution: Done > Not possible to set Google API level > ------------------------------------ > > Key: ARQ-1713 > URL: https://issues.jboss.org/browse/ARQ-1713 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > Priority: Blocker > Fix For: droidium_1.0.0.Alpha5 > > > *When*: > I want to setup a google API as target, for instance to run VM capable to work with GCM. > *Then*: > I can use apiLevel property, but this expects only integer and concatenes it with android-. > So, it is not possible to set that at all. > *Additional information*: > We need a more flexible way how to set that. I'm proposing removing *apiLevel* property and replace it with *target* > So, definitions would look like: > * apiLevel=19 => target=android-19 > * target=Google Inc.:Google APIs:19 -- 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 From issues at jboss.org Thu Mar 27 08:34:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Thu, 27 Mar 2014 08:34:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1728: -------------------------------------- Summary: Add possibility to report AS console output related to test methods Key: ARQ-1728 URL: https://issues.jboss.org/browse/ARQ-1728 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Recorder Affects Versions: recorder_1.0.0.Alpha3 Reporter: Stefan Miklosovic There is not any possiblity to see what AS has written out to console with test methods. Investigate a way how to match output from AS with particular test method during which that console output has occured. -- 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 From issues at jboss.org Thu Mar 27 08:54:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Thu, 27 Mar 2014 08:54:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1728) Add possibility to report AS console output related to test methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12956983#comment-12956983 ] Karel Piwko commented on ARQ-1728: ---------------------------------- It should be possible to provide a logger implementation that is able to fire events to Recorder. Or at least log into a location where recorder can pick it up. > Add possibility to report AS console output related to test methods > ------------------------------------------------------------------- > > Key: ARQ-1728 > URL: https://issues.jboss.org/browse/ARQ-1728 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha3 > Reporter: Stefan Miklosovic > > There is not any possiblity to see what AS has written out to console with test methods. > Investigate a way how to match output from AS with particular test method during which that console output has occured. -- 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 From issues at jboss.org Thu Mar 27 10:16:13 2014 From: issues at jboss.org (Nichole Stewart (JIRA)) Date: Thu, 27 Mar 2014 10:16:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1729) Add ability to deploy application to WAS Liberty server.xml file In-Reply-To: References: Message-ID: Nichole Stewart created ARQ-1729: ------------------------------------ Summary: Add ability to deploy application to WAS Liberty server.xml file Key: ARQ-1729 URL: https://issues.jboss.org/browse/ARQ-1729 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Nichole Stewart Assignee: Gerhard Poul Add ability to deploy application to WAS Liberty server.xml file in addition to the dropins directory. Additionally this will allow the usage of the shared library feature of Liberty. -- 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 From issues at jboss.org Thu Mar 27 11:16:14 2014 From: issues at jboss.org (Nichole Stewart (JIRA)) Date: Thu, 27 Mar 2014 11:16:14 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1729) Add ability to deploy application to WAS Liberty server.xml file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nichole Stewart updated ARQ-1729: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/16 > Add ability to deploy application to WAS Liberty server.xml file > ---------------------------------------------------------------- > > Key: ARQ-1729 > URL: https://issues.jboss.org/browse/ARQ-1729 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Nichole Stewart > Assignee: Gerhard Poul > > Add ability to deploy application to WAS Liberty server.xml file in addition to the dropins directory. Additionally this will allow the usage of the shared library feature of Liberty. -- 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 From issues at jboss.org Fri Mar 28 06:36:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 06:36:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1730) Repair unlocking of Android emulator In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1730: -------------------------------------- Summary: Repair unlocking of Android emulator Key: ARQ-1730 URL: https://issues.jboss.org/browse/ARQ-1730 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic Priority: Trivial -- 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 From issues at jboss.org Fri Mar 28 06:36:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 06:36:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1730) Repair unlocking of Android emulator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1730: -------------------------------------- Assignee: Stefan Miklosovic > Repair unlocking of Android emulator > ------------------------------------ > > Key: ARQ-1730 > URL: https://issues.jboss.org/browse/ARQ-1730 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > -- 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 From issues at jboss.org Fri Mar 28 07:26:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 07:26:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1731) Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1731: -------------------------------------- Summary: Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 Key: ARQ-1731 URL: https://issues.jboss.org/browse/ARQ-1731 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Fri Mar 28 07:28:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 07:28:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1731) Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1731: -------------------------------------- Assignee: Stefan Miklosovic > Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 > ------------------------------------------ > > Key: ARQ-1731 > URL: https://issues.jboss.org/browse/ARQ-1731 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- 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 From issues at jboss.org Fri Mar 28 07:36:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 07:36:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1731) Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1731. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha5 Resolution: Done https://github.com/arquillian/arquillian-droidium/commit/9df888b4f188c6dc059b51bea67164c073c12238 > Bump to Shrinkwrap 1.2.2 and ddmlib 22.7.2 > ------------------------------------------ > > Key: ARQ-1731 > URL: https://issues.jboss.org/browse/ARQ-1731 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Fri Mar 28 07:36:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 07:36:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1730) Repair unlocking of Android emulator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated ARQ-1730: ----------------------------------- Fix Version/s: droidium_1.0.0.Alpha5 > Repair unlocking of Android emulator > ------------------------------------ > > Key: ARQ-1730 > URL: https://issues.jboss.org/browse/ARQ-1730 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Fri Mar 28 07:38:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Fri, 28 Mar 2014 07:38:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1730) Repair unlocking of Android emulator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1730. ------------------------------------ Resolution: Done https://github.com/arquillian/arquillian-droidium/commit/e56b31756187e757475713543cff9877dee0481f > Repair unlocking of Android emulator > ------------------------------------ > > Key: ARQ-1730 > URL: https://issues.jboss.org/browse/ARQ-1730 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Priority: Trivial > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Fri Mar 28 08:46:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 28 Mar 2014 08:46:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: Juraj H?ska created ARQGRA-432: ---------------------------------- Summary: guardAjax does not work with XHR2 requests Key: ARQGRA-432 URL: https://issues.jboss.org/browse/ARQGRA-432 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 2.0.2.Final Reporter: Juraj H?ska {{guardAjax}} does not work correctly with XHR2 requests. The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- 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 From issues at jboss.org Fri Mar 28 08:50:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 28 Mar 2014 08:50:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated ARQGRA-432: ------------------------------- Description: {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. was: {{guardAjax}} does not work correctly with XHR2 requests. The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- 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 From issues at jboss.org Fri Mar 28 08:52:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 28 Mar 2014 08:52:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-432) guardAjax does not work with XHR2 requests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957332#comment-12957332 ] Juraj H?ska commented on ARQGRA-432: ------------------------------------ I have pushed test case for this [here|https://github.com/jhuska/arquillian-graphene/tree/ARQGRA-432]. * The {{.html}} page reproducing the issue, [here|https://github.com/jhuska/arquillian-graphene/blob/14a778b6f7720df761969cc630a59748f25a46f2/ftest/src/test/resources/org/jboss/arquillian/graphene/ftest/guard/xhr2.html]. * test, [here|https://github.com/jhuska/arquillian-graphene/blob/14a778b6f7720df761969cc630a59748f25a46f2/ftest/src/test/java/org/jboss/arquillian/graphene/ftest/guard/TestXHR2.java] > guardAjax does not work with XHR2 requests > ------------------------------------------ > > Key: ARQGRA-432 > URL: https://issues.jboss.org/browse/ARQGRA-432 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.2.Final > Reporter: Juraj H?ska > > {{guardAjax}} does not work correctly with XHR2 requests. The request is guarded correctly, but the callback once it is completed is not called. > The problem seems to be with {{onload}} (since XHR2) vs. {{onreadystatechange}} (since XHR1) callbacks. -- 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 From issues at jboss.org Sun Mar 30 18:20:13 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:20:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1654. -------------------------------- Fix Version/s: 1.1.4.Final (was: 2.0.0.Beta1) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/f8ec8e37bc8d1a195e84199816a2bf9e86129f26 > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit\(\*\) methods should probably be enough. -- 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 From issues at jboss.org Sun Mar 30 18:24:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:24:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1732) Support the use of Future from ExecutorService in InstanceProducer In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1732: ---------------------------------- Summary: Support the use of Future from ExecutorService in InstanceProducer Key: ARQ-1732 URL: https://issues.jboss.org/browse/ARQ-1732 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.4.Final Reporter: Aslak Knutsen Fix For: 2.0.0.Beta1 Open InstanceProducer with a option to set(Future). @Inject Instance inst; inst.get() would call future.get(); Would allow for background creation of any exposed contextual object. {code} @Inject @TestScoped private InstanceProducer producer; @Inject private Instance executor; producer.set(executor.submit(Callable)) {code} Questions: When is fire(T) called, when set(Future) as now, or when Future is resovled? -- 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 From issues at jboss.org Sun Mar 30 18:32:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:32:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1733: ---------------------------------- Summary: Update to latest ShrinkWrap|Resolver Key: ARQ-1733 URL: https://issues.jboss.org/browse/ARQ-1733 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.3.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.4.Final -- 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 From issues at jboss.org Sun Mar 30 18:36:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:36:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen resolved ARQ-1733. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/392e24422d40c8df573c3aaf833a2b5c9efa18ba > Update to latest ShrinkWrap|Resolver > ------------------------------------ > > Key: ARQ-1733 > URL: https://issues.jboss.org/browse/ARQ-1733 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > -- 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 From issues at jboss.org Sun Mar 30 18:38:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:38:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1733. ------------------------------ > Update to latest ShrinkWrap|Resolver > ------------------------------------ > > Key: ARQ-1733 > URL: https://issues.jboss.org/browse/ARQ-1733 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > -- 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 From issues at jboss.org Sun Mar 30 18:38:13 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:38:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1012) org.junit.Assume API not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1012. ------------------------------ > org.junit.Assume API not working > -------------------------------- > > Key: ARQ-1012 > URL: https://issues.jboss.org/browse/ARQ-1012 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Integration Test Suite > Affects Versions: 1.0.0.Final > Environment: Windows 7, Java 1.7 > Reporter: Karsten Ohme > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Hi, > my test classes are annotated with @RunWith(Arquillian.class) > I try to use the newer JUnit org.junit.Assume API. > The problem ist, that the outcome of the test seems to be ignored, e.g. org.junit.Assume.assertNonNull does not fail and throws an exception. -- 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 From issues at jboss.org Sun Mar 30 18:38:13 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:38:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1654. ------------------------------ > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit\(\*\) methods should probably be enough. -- 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 From issues at jboss.org Sun Mar 30 18:38:13 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:38:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1071. ------------------------------ > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final, 1.1.3.Final > Reporter: Rick-Rainer Ludwig > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {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 From issues at jboss.org Sun Mar 30 18:38:13 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Sun, 30 Mar 2014 18:38:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1641) Tests with failed assumptions do not show up as skipped In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aslak Knutsen closed ARQ-1641. ------------------------------ > Tests with failed assumptions do not show up as skipped > ------------------------------------------------------- > > Key: ARQ-1641 > URL: https://issues.jboss.org/browse/ARQ-1641 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > A test like this reports success instead of skipped. > Occurs with managed wildfly, tomcat, karaf > {code} > @Test > public void foo() throws Exception { > Assume.assumeTrue(false); > > // test code that should only run when the above is true > } > {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 From issues at jboss.org Mon Mar 31 04:16:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 04:16:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1712) Support for process identification In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1712: ----------------------------- Summary: Support for process identification (was: Support for process identification/timespamp) Fix Version/s: spacelift_1.0.0.Alpha2 Description: Spacelift currently always outputs process identification (based on first argument). It should be possible to: * make this string configurable * disable this altogether This will help make logs more readable. was: Spacelift currently always outputs process identification (based on first argument). It should be possible to: * make this string configurable * disable this altogether * add timestamp to the output There should be both API and system property approach - for disabling and timespamps. This will help make logs more readable. Assignee: Karel Piwko > Support for process identification > ---------------------------------- > > Key: ARQ-1712 > URL: https://issues.jboss.org/browse/ARQ-1712 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Spacelift currently always outputs process identification (based on first argument). > It should be possible to: > * make this string configurable > * disable this altogether > This will help make logs more readable. -- 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 From issues at jboss.org Mon Mar 31 04:18:12 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 04:18:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1712) Support for process identification In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1712. ------------------------------ Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-spacelift/commit/413cdd0f605a5d6dc9e2c2fe127a90500fcaf15c > Support for process identification > ---------------------------------- > > Key: ARQ-1712 > URL: https://issues.jboss.org/browse/ARQ-1712 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Spacelift currently always outputs process identification (based on first argument). > It should be possible to: > * make this string configurable > * disable this altogether > This will help make logs more readable. -- 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 From issues at jboss.org Mon Mar 31 05:10:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 31 Mar 2014 05:10:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1734) Update Droidium to use Arquillian Core 1.1.4 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1734: -------------------------------------- Summary: Update Droidium to use Arquillian Core 1.1.4 Key: ARQ-1734 URL: https://issues.jboss.org/browse/ARQ-1734 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Mon Mar 31 05:12:12 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 31 Mar 2014 05:12:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1734) Update Droidium to use Arquillian Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1734: -------------------------------------- Assignee: Stefan Miklosovic > Update Droidium to use Arquillian Core 1.1.4 > -------------------------------------------- > > Key: ARQ-1734 > URL: https://issues.jboss.org/browse/ARQ-1734 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- 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 From issues at jboss.org Mon Mar 31 05:12:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 31 Mar 2014 05:12:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1734) Update Droidium to use Arquillian Core 1.1.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic resolved ARQ-1734. ------------------------------------ Fix Version/s: droidium_1.0.0.Alpha5 Resolution: Done https://github.com/arquillian/arquillian-droidium/commit/7e39b5ffb5c359fe935ba711e4b4b6b8e55e2992 > Update Droidium to use Arquillian Core 1.1.4 > -------------------------------------------- > > Key: ARQ-1734 > URL: https://issues.jboss.org/browse/ARQ-1734 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- 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 From issues at jboss.org Mon Mar 31 06:32:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 06:32:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Remove temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1669: -------------------------------- Assignee: Karel Piwko > Remove temporary workaround for Executor Service > ------------------------------------------------ > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.CR1 > > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 31 07:00:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 07:00:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Remove temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1669: ----------------------------- Fix Version/s: (was: drone_2.0.0.CR1) > Remove temporary workaround for Executor Service > ------------------------------------------------ > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 31 07:00:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 07:00:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Remove temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1669: ----------------------------- Fix Version/s: drone_2.0.0.Alpha1 > Remove temporary workaround for Executor Service > ------------------------------------------------ > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 31 07:06:13 2014 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 31 Mar 2014 07:06:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1669) Remove temporary workaround for Executor Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko resolved ARQ-1669. ------------------------------ Resolution: Done Resolved by updating Arquillian Core to 1.1.4.Final. Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/b85d3fdc5f9015f15ffad0ac8899f7014a9d6ce8 > Remove temporary workaround for Executor Service > ------------------------------------------------ > > Key: ARQ-1669 > URL: https://issues.jboss.org/browse/ARQ-1669 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, drone_1.2.4.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_2.0.0.Alpha1 > > > Remove temporary workaround for ARQ-1654 once it becomes available in Core. -- 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 From issues at jboss.org Mon Mar 31 15:13:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 31 Mar 2014 15:13:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1735) Release Droidium 1.0.0.Alpha5 In-Reply-To: References: Message-ID: Stefan Miklosovic created ARQ-1735: -------------------------------------- Summary: Release Droidium 1.0.0.Alpha5 Key: ARQ-1735 URL: https://issues.jboss.org/browse/ARQ-1735 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Extension - Droidium Affects Versions: droidium_1.0.0.Alpha4 Reporter: Stefan Miklosovic -- 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 From issues at jboss.org Mon Mar 31 15:13:13 2014 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Mon, 31 Mar 2014 15:13:13 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1735) Release Droidium 1.0.0.Alpha5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic reassigned ARQ-1735: -------------------------------------- Assignee: Stefan Miklosovic > Release Droidium 1.0.0.Alpha5 > ----------------------------- > > Key: ARQ-1735 > URL: https://issues.jboss.org/browse/ARQ-1735 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > -- 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 From issues at jboss.org Mon Mar 31 22:21:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 31 Mar 2014 22:21:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1736) Make defaultServer the default serverName in WLP Managed In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1736: ---------------------------------- Summary: Make defaultServer the default serverName in WLP Managed Key: ARQ-1736 URL: https://issues.jboss.org/browse/ARQ-1736 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: WebSphere Containers Affects Versions: wls_1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Gerhard Poul If serverName is missing from arquillian.xml, the container die with a NullPointerException in validate. Should default to 'defaultServer' for a better startup experience. -- 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 From issues at jboss.org Mon Mar 31 22:27:12 2014 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 31 Mar 2014 22:27:12 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1737) Missing Container Configuration cause NullPointerException in validate In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1737: ---------------------------------- Summary: Missing Container Configuration cause NullPointerException in validate Key: ARQ-1737 URL: https://issues.jboss.org/browse/ARQ-1737 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: WebSphere Containers Affects Versions: was_1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Gerhard Poul serverName, wlpHomeDir, sharedLib httpPort should default to the default port used by wlp -- 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