[JBoss JIRA] (ARQ-1179) Mark a test so it will only run against certain browsers
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1179?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1179:
-----------------------------
Fix Version/s: drone_2.0.0.Alpha4
(was: drone_2.0.0.Alpha3)
> Mark a test so it will only run against certain browsers
> --------------------------------------------------------
>
> Key: ARQ-1179
> URL: https://issues.jboss.org/browse/ARQ-1179
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Reporter: Brian Leathem
> Fix For: drone_2.0.0.Alpha4
>
>
> It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers.
> Some sample use cases:
> # Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance)
> # Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1545) Drone: allow to setup WebDriver's Capabilities programatically
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1545?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1545:
-----------------------------
Fix Version/s: drone_2.0.0.Alpha4
(was: drone_2.0.0.Alpha3)
> Drone: allow to setup WebDriver's Capabilities programatically
> --------------------------------------------------------------
>
> Key: ARQ-1545
> URL: https://issues.jboss.org/browse/ARQ-1545
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.2.0.Final
> Reporter: Lukáš Fryč
> Fix For: drone_2.0.0.Alpha4
>
>
> The programatic configuration comes when some capability is unsupported and it has complex type, such as collection or array.
> ----
> Even though I can access WebDriverConfiguration programatically and retrieve #getCapabilities(), I will get clone of capabilities stored in configuration.
> I suggest we allow to access capabilityMap in order to allow programatically configure.
> ----
> Please document a sample of usage here once done, i.e. what even is expected to listen.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1032) Drone: shortcut for starting Selenium Server
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1032?page=com.atlassian.jira.plugin.s... ]
Karel Piwko updated ARQ-1032:
-----------------------------
Fix Version/s: drone_2.0.0.Alpha4
(was: drone_2.0.0.Alpha3)
> Drone: shortcut for starting Selenium Server
> --------------------------------------------
>
> Key: ARQ-1032
> URL: https://issues.jboss.org/browse/ARQ-1032
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.CR1
> Reporter: Lukáš Fryč
> Fix For: drone_2.0.0.Alpha4
>
>
> When starting Drone test development, user needs to obtain appropriate version of {{selenium-server.jar}}, start it with {{java}} and provide all necessary properties like {{chrome.driver.binary}}.
> Required information is already available in {{pom.xml}} (selenium version) and {{arquillian.xml}} (driver properties).
> To allow quick bootstrap, Drone should provide method for user to ramp up to development quickly.
> Following integration can be considered:
> * JBDS
> * Forge - {{drone start}}
> * Maven - {{mvn arquillian:drone-start}}
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1749) auto discover httpPort from Container
by Gerhard Poul (JIRA)
[ https://issues.jboss.org/browse/ARQ-1749?page=com.atlassian.jira.plugin.s... ]
Gerhard Poul updated ARQ-1749:
------------------------------
Assignee: (was: Gerhard Poul)
> auto discover httpPort from Container
> -------------------------------------
>
> Key: ARQ-1749
> URL: https://issues.jboss.org/browse/ARQ-1749
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: WebSphere Containers
> Affects Versions: was_1.0.0.Alpha2
> Reporter: Aslak Knutsen
>
> The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml.
> The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1749) auto discover httpPort from Container
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1749:
----------------------------------
Summary: auto discover httpPort from Container
Key: ARQ-1749
URL: https://issues.jboss.org/browse/ARQ-1749
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WebSphere Containers
Affects Versions: was_1.0.0.Alpha2
Reporter: Aslak Knutsen
Assignee: Gerhard Poul
The exposed MBean WebSphere/endpoint/channelfw/defaultHttpEndpoint contain Host and Port attributes which could be used if httpPort is not configured in arquillian.xml.
The Container require serverName to detect which VM is running, and as long as you have the VM you have the httpPort info. Defaulting to the 'defaultHttpEndpoint' should remove a few possible error configurations.
--
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
10 years, 9 months