We should know that Drone supports all the listed browsers with all the features like:
on following browsers:
- Internet Explorer
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:
support for configurating arquillian.xml during runtime for matrix browser compability jobs
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
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.