[JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.s... ]
Matous Jobanek closed ARQ-1890.
-------------------------------
Resolution: Done
solved by https://github.com/arquillian/arquillian-extension-drone/commit/3914bc009...
> Support implementation of Microsoft WebDriver
> ---------------------------------------------
>
> Key: ARQ-1890
> URL: https://issues.jboss.org/browse/ARQ-1890
> Project: Arquillian
> Issue Type: Feature Request
> Components: Extension - Drone
> Affects Versions: drone_1.3.1.Final
> Reporter: Sona Jamborova
> Assignee: Tomas David
> Fix For: drone_2.1.0.Final
>
>
> Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium.
> My Idea is:
> 1) An user is responsible to install MS WebDriver
> 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT.
> Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments).
> Solution for branch drone 1.3.x:
> * for enabling property in arquillian.xml:
> ** add new field (attribute) in class WebDriverConfiguration
> ** add setter and getter for this field
> ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class
> * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine"
> ** in class InternetExplorerDriverFactory
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months
[JBoss JIRA] (ARQ-1890) Support implementation of Microsoft WebDriver
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/ARQ-1890?page=com.atlassian.jira.plugin.s... ]
Matous Jobanek reassigned ARQ-1890:
-----------------------------------
Assignee: Tomas David
> Support implementation of Microsoft WebDriver
> ---------------------------------------------
>
> Key: ARQ-1890
> URL: https://issues.jboss.org/browse/ARQ-1890
> Project: Arquillian
> Issue Type: Feature Request
> Components: Extension - Drone
> Affects Versions: drone_1.3.1.Final
> Reporter: Sona Jamborova
> Assignee: Tomas David
> Fix For: drone_2.1.0.Final
>
>
> Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium.
> My Idea is:
> 1) An user is responsible to install MS WebDriver
> 2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT.
> Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments).
> Solution for branch drone 1.3.x:
> * for enabling property in arquillian.xml:
> ** add new field (attribute) in class WebDriverConfiguration
> ** add setter and getter for this field
> ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class
> * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine"
> ** in class InternetExplorerDriverFactory
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months
[JBoss JIRA] (ARQGRA-495) Scheme and URL properties might be used in incompatible ways
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-495?page=com.atlassian.jira.plugin... ]
Matous Jobanek updated ARQGRA-495:
----------------------------------
Fix Version/s: 2.2.0
> Scheme and URL properties might be used in incompatible ways
> ------------------------------------------------------------
>
> Key: ARQGRA-495
> URL: https://issues.jboss.org/browse/ARQGRA-495
> Project: Arquillian Graphene
> Issue Type: Bug
> Reporter: Alex Soto
> Assignee: Alex Soto
> Priority: Minor
> Fix For: 2.2.0
>
>
> Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently.
> The ideal scenario would be that URL protocol takes precedence over scheme
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 11 months