[JBoss JIRA] (ARQGRA-226) graphene-webdriver-ftest cleanup for reference usage
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-226?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-226:
------------------------------
Fix Version/s: 2.0-Tracking
(was: 2.0.0.Beta1)
> graphene-webdriver-ftest cleanup for reference usage
> ----------------------------------------------------
>
> Key: ARQGRA-226
> URL: https://issues.jboss.org/browse/ARQGRA-226
> Project: Arquillian Graphene
> Issue Type: Enhancement
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Trivial
> Fix For: 2.0-Tracking
>
>
> {{graphene-webdriver-ftest}} should be used as reference usage for Graphene, thus we need to:
> * remove dependency on {{arquillian-test-impl-base}}
> * remove dependencies which are commented out
> * add comments
> ** on depchain - it brings all the dependencies
> ** on arquillian-junit-standalone - explain what dependencies might be used instead {{arquillian-{testng,junit}-{standalone,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
11 years, 3 months
[JBoss JIRA] (ARQGRA-117) Create JBoss Forge plugin for Graphene
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-117?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-117:
------------------------------
Fix Version/s: 2.0-Tracking
(was: 2.0.0.Beta1)
> Create JBoss Forge plugin for Graphene
> --------------------------------------
>
> Key: ARQGRA-117
> URL: https://issues.jboss.org/browse/ARQGRA-117
> Project: Arquillian Graphene
> Issue Type: Task
> Components: integration
> Reporter: Lukáš Fryč
> Priority: Critical
> Labels: devconf
> Fix For: 2.0-Tracking
>
>
> This could be rather Arquillian/Drone plugin.
> Requirements:
> * scaffolding new Graphene project
> * start remote selenium server (ARQ-1032)
> * ability to export @Deployment
> ** the export of deployment is afaik done in Arquillian Forge plugin
> * ability to deploy @Deployment (export + deploy) (ARQGRA-213)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (ARQ-1209) Abbreviate WebDriver configuration property browserCapabilities as browser
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1209?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1209:
-----------------------------
Fix Version/s: drone_1.2.0.next
(was: drone_1.2.0.Alpha3)
> Abbreviate WebDriver configuration property browserCapabilities as browser
> --------------------------------------------------------------------------
>
> Key: ARQ-1209
> URL: https://issues.jboss.org/browse/ARQ-1209
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.Final
> Reporter: Dan Allen
> Labels: starter
> Fix For: drone_1.2.0.next
>
>
> Story:
> *In order to* save typing and make the WebDriver configuration more readable
> *As a* tester
> *I want to* be able to configure the browser using the property name "browser" instead of "browserCapabilities"
> Scenarios:
> *Given* I want to use the FirefoxDriver when running my Drone WebDriver tests
> *When* I set the browser (e.g., firefox) in the WebDriver configuration property named "browser"
> *Then* Drone should interpret the value of that property as the browserCapabilities
> ; *And* Drone should select and initialize the FirefoxDriver
> ; *And* Drone should inject the FirefoxDriver into the @Drone injection point in the test
> *Given* I want to use the FirefoxDriver when running my Drone WebDriver tests
> : *And* I have an existing Drone WebDriver configuration
> *When* I set the browser (e.g., firefox) in the WebDriver configuration property named "browserCapabilities"
> *Then* Drone should interpret the value of that property as the browserCapabilities
> ; *And* Drone should select and initialize the FirefoxDriver
> ; *And* Drone should inject the FirefoxDriver into the @Drone injection point in the test
> Rationale:
> While browserCapabilities is the official name for specifying the browser by its coordinates name, version and platform, we need not expose this formality to our users. We can honor both names for this property, perhaps throwing an exception if both are present. Once we sort that out, we should propose another scenario to cover 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
11 years, 3 months
[JBoss JIRA] (ARQ-1062) Arquillian Drone Webdriver's OperaDriver depchain is not compatible with ShrinkWrap Resolver 1.0.0-beta-7
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1062?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1062.
----------------------------
Assignee: Karel Piwko
Resolution: Out of Date
This issue is fixed by updating Arquillian Core to 1.1.0.Final, which brings SWR 2.0.0 in ARQ-1435
> Arquillian Drone Webdriver's OperaDriver depchain is not compatible with ShrinkWrap Resolver 1.0.0-beta-7
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1062
> URL: https://issues.jboss.org/browse/ARQ-1062
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.CR2
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Fix For: drone_1.2.0.Alpha3
>
>
> When using OperaDriver defined in org.jboss.arquillian.extension:arquillian-drone-webdriver-depchain, together with ShrinkWrap Resolver on the classpath,
> following error might occur, depending on classpath ordering:
> {code}
> java.lang.RuntimeException: Unable to instantiate Drone via com.opera.core.systems.OperaDriver(Capabilities)
> at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:160)
> at org.jboss.arquillian.drone.webdriver.factory.OperaDriverFactory.createInstance(OperaDriverFactory.java:70)
> at org.jboss.arquillian.drone.webdriver.factory.OperaDriverFactory.createInstance(OperaDriverFactory.java:35)
> at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129)
> at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43)
> at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.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.DroneConfigurator.configureDrone(DroneConfigurator.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java: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:90)
> 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:90)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
> Caused by: java.lang.NoSuchMethodError: com.google.common.base.Platform.precomputeCharMatcher(Lcom/google/common/base/CharMatcher;)Lcom/google/common/base/CharMatcher;
> at com.google.common.base.CharMatcher.precomputed(CharMatcher.java:719)
> at com.google.common.base.CharMatcher.<clinit>(CharMatcher.java:66)
> at com.google.common.base.CaseFormat.<clinit>(CaseFormat.java:32)
> at com.opera.core.systems.OperaSettings$Capability.<init>(OperaSettings.java:456)
> at com.opera.core.systems.OperaSettings$Capability.<init>(OperaSettings.java:110)
> at com.opera.core.systems.OperaSettings$Capability$1.<init>(OperaSettings.java:121)
> at com.opera.core.systems.OperaSettings$Capability.<clinit>(OperaSettings.java:121)
> at com.opera.core.systems.OperaSettings.<init>(OperaSettings.java:571)
> at com.opera.core.systems.OperaDriver.<init>(OperaDriver.java:160)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:142)
> ... 58 more
> {code}
> This happens due to com.google.common.base.Platform being included in guava-12 (RemoteWebDriver dependency) and google-collections (ShrinkWrap Resolver dependency)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (ARQ-1040) The properties of container configuration in arquillian.xml are not parsed properly
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1040?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen closed ARQ-1040.
------------------------------
> The properties of container configuration in arquillian.xml are not parsed properly
> -----------------------------------------------------------------------------------
>
> Key: ARQ-1040
> URL: https://issues.jboss.org/browse/ARQ-1040
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Configuration
> Affects Versions: 1.0.1.Final
> Reporter: Tomas Repel
> Fix For: 1.1.1.Final
>
>
> It is impossible to use tabs or newlines in arquillian.xml when defining properties for tomcat configuration. Only space (" ") can be used as delimiter.
> For example, this configuration is OK:
> {code:xml}
> <container qualifier="tomcat" default="true">
> <configuration>
> <property name="catalinaHome">/home/tomcat6</property>
> <property name="javaVmArguments">-Xmx1024m -XX:MaxPermSize=512</property>
> </configuration>
> </container>
> {code}
> While this one causes failure on startup:
> {code:xml}
> <container qualifier="tomcat" default="true">
> <configuration>
> <property name="catalinaHome">/home/tomcat6</property>
> <property name="javaVmArguments">
> -Xmx1024m
> -XX:MaxPermSize=512
> </property>
> </configuration>
> </container>
> {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
11 years, 3 months