[
https://issues.jboss.org/browse/JBIDE-16285?page=com.atlassian.jira.plugi...
]
Lukáš Fryč commented on JBIDE-16285:
------------------------------------
The use case is support of reusable sessions that:
* speeds up test development (the difference is similar to difference between managed and
remote Arquillian container modes)
* allows in-browser debugging of Selenium tests (again, similar to remote container in
debugging mode)
----
We could either:
* let an user point to {{selenium-server-standalone.jar}} binary and phantomjs[.exe]
binary manually
* detect the artifacts on classpath in one of opened projects - here we could depend on
presence of Arquillian Drone - so the only dependency between JBoss Tools and Selenium
would be Drone API
A right solution highly depends on requirements (e.g. minimize maintanance efforts on
JBoss Tools side, leveraging classpath resolution, hooking up Drone API),
so I would prefer to discuss possibilities once we know whether we want something like
this in JBDS or not.. ;-)
Support for Selenium Server adapter
-----------------------------------
Key: JBIDE-16285
URL:
https://issues.jboss.org/browse/JBIDE-16285
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing-tools
Reporter: Lukáš Fryč
Fix For: LATER
Running Selenium Server remotely is integral part of Arquillian Drone workflow for
authoring
[
Selenium/WebDriver/Graphene|https://docs.jboss.org/author/display/ARQGRA2...]
based tests (both are part of WFK), leveraging [Drone Reusable Browser
Session|https://docs.jboss.org/author/display/ARQGRA2/Using+Drone?_sscc=t...]
feature.
The idea is having a Selenium Server as a server adapter in Servers view (similarly to
Livereload server adapter).
----
Available actions:
* start/stop/restart
* kill all running browsers
** there is [well-defined (RESTful)
API|https://code.google.com/p/selenium/wiki/JsonWireProtocol#/sessions called
JsonWireProtocol] for controlling the Selenium Server
* eventually selecting a browser to run tests against (e.g. PhantomJS in (now it is
leveraged via arquillian.xml configuration)
Configuration options:
* select [{{selenium-server-standalone.jar}}|http://docs.seleniumhq.org/download/] to
run
** upgrades of Selenium are necessary because of browser-compatibility reasons
** there could be even an option for downloading newer versions automatically
Advanced features:
* debugging support for PhantomJS browser driver (need to pass [remote debugging
arguments|https://github.com/ariya/phantomjs/wiki/Troubleshooting#remote-...])
--
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