[arquillian-issues] [JBoss JIRA] (ARQ-666) Redesign WebDriver browser configuration
[
https://issues.jboss.org/browse/ARQ-666?page=com.atlassian.jira.plugin.sy...
]
Karel Piwko commented on ARQ-666:
---------------------------------
We have two constraints here:
* We need to be able to switch between different WebDriver impls using arquillian.xml
only
* We need to know that some property is not valid for certain type of the browser
My idea here is to have a single backing class which will allow user to define all the
properties and restrict that via a list of interfaces which corresponds to a specific
drivers.
This means that:
User can specify anything he wants for <extension qualifier="webdriver">
And than use @Drone WebDriver driver; to get the instance specified by
implementationClass.
On the other way, if he says @Drone FirefoxDriver, the list of available system properties
will be restricted (e.g. a warning will be logged that is have no effect on the current
browser type)
Redesign WebDriver browser configuration
----------------------------------------
Key: ARQ-666
URL: https://issues.jboss.org/browse/ARQ-666
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.0.0.CR2
Reporter: Karel Piwko
Priority: Critical
Fix For: drone_1.0.0.Final
Current binding of browser type to the type defined in the class itself limits the usage
of generic WebDriver drivers.
This means that you can simply change WebDriver type by configuration, you have to modify
Java code. The usage should be modified to implementationClass be the property which
decides what instance will be used even for generic webdrivers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira