[
https://issues.jboss.org/browse/ARQ-951?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated ARQ-951:
---------------------------
Summary: Drone: Setup Matrix jobs for browser support (was: Setup Matrix jobs
for browser support)
Fix Version/s: drone_1.1.0.next
Component/s: Extension - Drone
Drone: Setup Matrix jobs for browser support
--------------------------------------------
Key: ARQ-951
URL:
https://issues.jboss.org/browse/ARQ-951
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Extension - Drone
Reporter: Lukáš Fryč
Fix For: drone_1.1.0.next
We should know that Drone supports all the listed browsers with all the features like:
* instantiation
* destruction
* reusability
on following browsers:
* HtmlUnit
* Firefox
* Chrome
* Internet Explorer
* Opera
* Android
* IPhone
This will make sure we are able to base our tests on @Drone in QA Lab and verify the
high-level functionality like reusability works for all the browsers.
----
The same needs to be addressed in scope of Graphene, see references:
ARQGRA-59
support for configurating arquillian.xml during runtime for matrix browser compability
jobs
ARQGRA-76
Setup matrix jobs for browser support
----
The problem with this approach is that we need to filter what we actually want to test.
I have identified following types of tetsts in Graphene suite:
* able to run in any continuous-integration
** unit tests
** arquillian core integration tests
** ftests able to run with htmlunit
* running only in specific environment
** browser-specific
We need to modify {{arquillian.xml}} in order to select appropriate browser for given
run.
Also, unit-tests shouldn't be run as part of ftests, since it is redundant.
--
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