August 2013 - arquillian-issues - Jboss List Archives

[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 edited comment on ARQ-1209 at 8/26/13 7:49 AM: ----------------------------------------------------------- browserCapabilities is now legacy value, it is deprecated and automatically mapped to "browser". If both properties are defined at the same time, the output is undefined, as it precedence depends on JDK internals. was (Author: kpiwko): browserCapabilities is now legacy value, it is deprecated and automatically mapped to "browser". If both properties are defined at the same time, the action is undefined, as it precedence depends on JDK internals. > 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 > Assignee: Karel Piwko > Labels: starter > Fix For: drone_1.2.0.Beta1 > > > 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, 4 months

1
0
0 / 0

[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 resolved ARQ-1209. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.0.Beta1 (was: drone_1.2.0.next) Resolution: Done Fixed in https://github.com/arquillian/arquillian-extension-drone/commit/2763c3727... > 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 > Assignee: Karel Piwko > Labels: starter > Fix For: drone_1.2.0.Beta1 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1460) Allow Drone instance creation timeout to be configurable

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1460?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1460. ------------------------------ Assignee: Karel Piwko Fix Version/s: drone_1.2.0.Beta1 Resolution: Done Fixed in https://github.com/arquillian/arquillian-extension-drone/commit/ee18fac05... > Allow Drone instance creation timeout to be configurable > -------------------------------------------------------- > > Key: ARQ-1460 > URL: https://issues.jboss.org/browse/ARQ-1460 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Beta1 > > > Current limit of 5 seconds for instance creation should be configurable. > Additionally, it should disable altogether via -Darquillian.debug=true -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1459) Update Drone to use Selenium 2.35.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1459?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1459: ----------------------------- Assignee: Karel Piwko > Update Drone to use Selenium 2.35.0 > ----------------------------------- > > Key: ARQ-1459 > URL: https://issues.jboss.org/browse/ARQ-1459 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1459) Update Drone to use Selenium 2.35.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1459?page=com.atlassian.jira.plugin.s... ] Karel Piwko resolved ARQ-1459. ------------------------------ Fix Version/s: drone_1.2.0.Beta1 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/9ccda6cd3... > Update Drone to use Selenium 2.35.0 > ----------------------------------- > > Key: ARQ-1459 > URL: https://issues.jboss.org/browse/ARQ-1459 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha3 > Reporter: Karel Piwko > Fix For: drone_1.2.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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1460) Allow Drone instance creation timeout to be configurable

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1460: -------------------------------- Summary: Allow Drone instance creation timeout to be configurable Key: ARQ-1460 URL: https://issues.jboss.org/browse/ARQ-1460 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.2.0.Alpha3 Reporter: Karel Piwko Current limit of 5 seconds for instance creation should be configurable. Additionally, it should disable altogether via -Darquillian.debug=true -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1459) Update Drone to use Selenium 2.35.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1459?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1459: ----------------------------- Affects Version/s: drone_1.2.0.Alpha3 > Update Drone to use Selenium 2.35.0 > ----------------------------------- > > Key: ARQ-1459 > URL: https://issues.jboss.org/browse/ARQ-1459 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Affects Versions: drone_1.2.0.Alpha3 > Reporter: Karel Piwko > -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1459) Update Drone to use Selenium 2.35.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1459?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1459: ----------------------------- Component/s: Extension - Drone > Update Drone to use Selenium 2.35.0 > ----------------------------------- > > Key: ARQ-1459 > URL: https://issues.jboss.org/browse/ARQ-1459 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha3 > Reporter: Karel Piwko > -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1459) Update Drone to use Selenium 2.35.0

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1459: -------------------------------- Summary: Update Drone to use Selenium 2.35.0 Key: ARQ-1459 URL: https://issues.jboss.org/browse/ARQ-1459 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Karel Piwko -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1456) Unable to authenticate to Tomcat 7 - illegal characters in header

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ARQ-1456?page=com.atlassian.jira.plugin.s... ] Martin Gencur resolved ARQ-1456. -------------------------------- Resolution: Rejected It appears that this problem can be solved by adding commons-coded dependency to the project, as described at https://community.jboss.org/message/779751 > Unable to authenticate to Tomcat 7 - illegal characters in header > ----------------------------------------------------------------- > > Key: ARQ-1456 > URL: https://issues.jboss.org/browse/ARQ-1456 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Martin Gencur > > I'm constantly getting the following exception when starting a managed Tomcat container (Tomcat 7): > {code} > java.lang.IllegalArgumentException: Illegal character(s) in message header value: Basic YWRtaW46YWRtaW4= > at sun.net.www.protocol.http.HttpURLConnection.checkMessageHeader(HttpURLConnection.java:482) > at sun.net.www.protocol.http.HttpURLConnection.isExternalMessageHeaderAllowed(HttpURLConnection.java:434) > at sun.net.www.protocol.http.HttpURLConnection.setRequestProperty(HttpURLConnection.java:2752) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.execute(CommonTomcatManager.java:214) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.list(CommonTomcatManager.java:116) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.isRunning(CommonTomcatManager.java:123) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:85) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > 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:601) > 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.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > 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:601) > 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.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > 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:601) > 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:86) > 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:601) > 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.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 java.lang.reflect.Method.invoke(Method.java:601) > 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.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > 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:601) > 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:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > The configuration of the container in arquillian.xml looks like this: > {code} > <container qualifier="server1" default="true"> > <configuration> >  > <property name="jmxPort">8089</property> > <property name="bindHttpPort">8080</property> > <property name="catalinaHome">${tomcat.home}</property> > <property name="user">admin</property> > <property name="pass">admin</property> > </configuration> > </container> > {code} > and I indeed configured the right credentials in tomcat-users.xml: > {code} > <tomcat-users> > <role rolename="manager-script"/> > <user username="admin" password="admin" roles="manager-script"/> > </tomcat-users> > {code} > It does not matter which username or password I use as long as they're the same in arquillian.xml and tomcat-users.xml > I found a similar problem and possible solution at https://forums.oracle.com/thread/2200463?start=0&tstart=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

11 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2013