September 2014 - arquillian-issues

[JBoss JIRA] (ARQGRA-430) Setup continous integration of 2.1 branch

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-430?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-430. ------------------------------- Assignee: Lukáš Fryč Resolution: Won't Fix > 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č > Assignee: Lukáš Fryč > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-415) Cloudbees matrix job fails with NPE

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-415?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-415. ------------------------------- Assignee: Lukáš Fryč Resolution: Won't Fix > Cloudbees matrix job fails with NPE > ----------------------------------- > > Key: ARQGRA-415 > URL: https://issues.jboss.org/browse/ARQGRA-415 > Project: Arquillian Graphene > Issue Type: Task > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > > https://arquillian.ci.cloudbees.com/job/arquillian-graphene-webdriver-fte... > {code} > Error Message > Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive() > Stacktrace > java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive() > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:177) > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:99) > 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: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.client.ContainerEventController.execute(ContainerEventController.java:100) > 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.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > 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:60) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > 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.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:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: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:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) > Caused by: java.lang.reflect.InvocationTargetException > 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.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:173) > ... 54 more > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.graphene.ftest.Resource$ResourceBuilder.all(Resource.java:81) > at org.jboss.arquillian.graphene.ftest.Resources.all(Resources.java:65) > at org.jboss.arquillian.graphene.ftest.condition.ConditionsTestCase.createTestArchive(ConditionsTestCase.java:79) > ... 59 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-461) Running Graphene tests and use parallelStream method makes test fail with java.lang.IllegalStateException: The Graphene runtime isn't initialized. Exception.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-461?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-461. ------------------------------- Assignee: Lukáš Fryč Resolution: Rejected Agree, {{parallelStream()}} is in Selenium / Graphene 2.x a misuse that is expected to lead into threading issues. If there would be really an elevated need, we may re-consider allowing such a usage by propagating contexts. Thanks for describing the issue though, Alex, at least for future reference, as you say! > Running Graphene tests and use parallelStream method makes test fail with java.lang.IllegalStateException: The Graphene runtime isn't initialized. Exception. > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ARQGRA-461 > URL: https://issues.jboss.org/browse/ARQGRA-461 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Alex Soto > Assignee: Lukáš Fryč > Priority: Minor > Labels: java8,, threads > > Running Graphene tests and use parallelStream method makes test fail with java.lang.IllegalStateException: The Graphene runtime isn't initialized. Exception. > Basically the problem is when you want to get information about tables. You can iterate over elements in a foreach fashion, but you can also use new Java 8 stream API. > This works: ession.findElements(xpath("//table/tbody/tr/td/span[@class='title']")).stream().map(WebElement::getText).collect(Collectors.toList()); > But if table is big you will try to improve parsing speed by adding parallelSteam (session.findElements(xpath("//table/tbody/tr/td/span[@class='title']")).parallelStream().map(WebElement::getText).collect(Collectors.toList());) > And in this case an exception is thrown. > Internally parallelStream uses a pool of threads so probably Graphene instance is tight to thread of test case, so the threads used by parallelStream does not contains a valid instance of Graphene. > Of course this is not blocking nor a big problem in the sense that you can use stream() without any problem, and moreover Java 8 is not spread yet, but it may be a problem in the future. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-411) GrapheneElement methods should wait until element is present

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-411?page=com.atlassian.jira.plugin... ] Lukáš Fryč resolved ARQGRA-411. ------------------------------- Assignee: Lukáš Fryč Resolution: Incomplete Description > GrapheneElement methods should wait until element is present > ------------------------------------------------------------ > > Key: ARQGRA-411 > URL: https://issues.jboss.org/browse/ARQGRA-411 > Project: Arquillian Graphene > Issue Type: Feature Request > Reporter: Emil Cervenan > Assignee: Lukáš Fryč > > Scenarios when element is generated by javascript and performance is low leads to situations when method of element which is not present is called. Unwanted exception is thrown. When you are trying to simulate users behaviour it is clear you are not expecting clicking, typing and so on to elements which are not present. Therefore each GrapheneElement method should wait until element is present. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-409) Support for Ember.js

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-409: ----------------------------------- [~smikloso] [~kpiwko] I believe this extension is not requires at this point? Can I resolve this and see whether there will be a need for that in the future? > 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-sel... > http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-base... > I believe that such tools might be handy for angular.js testing as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and interaction synchronization

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin... ] Lukáš Fryč closed ARQGRA-427. ----------------------------- Assignee: Lukáš Fryč Resolution: Out of Date > 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č > Assignee: Lukáš Fryč > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-427) Support for AngularJS locators and interaction synchronization

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-427?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-427: ----------------------------------- This is enabled by extension https://github.com/arquillian/arquillian-extension-angularjs > 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 was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Ian Brandt closed ARQ-1846. --------------------------- > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Ian Brandt resolved ARQ-1846. ----------------------------- Resolution: Duplicate Issue Considering this as superseded by ARQ-1848 and resolving as a duplicate. > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Ian Brandt updated ARQ-1846: ---------------------------- Fix Version/s: (was: tomcat_1.0.0.Final) > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2014