This is a remote server implementation written in Clojure, to be used with the RobotFramework automated testing framework.
If you're using Leiningen and you just want to run the server using the small keyword library that comes with this code, run lein run at the command-line.
Once you're ready to run your own keyword library, read on.
In the namespace you've used to write your RobotFramework keyword library, include the following:
(use 'robot-remote-server.core)
(server-start! (init-handler))
This code should be placed inside the namespace that contains all your RobotFramework keywords; the init-handler macro generates a Ring handler that uses the current namespace to find RobotFramework keywords. Be not afraid to spread you namespace over multiple files using (in-ns 'name-of-namescape) and (load file_name) to make your keyword codebase more manageable.
The function server-start! accepts a third optional argument of true or false: true if you want to be able to stop the server remotely via an XML-RPC call to stop_remote_server or via the Stop Remote Server RobotFramework keyword, false if you do not want to expose this functionality to end users but instead will call the Clojure function server-stop! yourself or kill the process at the system level using Ctrl+C, C-c C-c or equivalent. The default is true to remain faithful to the RobotFramework spec and implementations in other languages.
The function also accepts an optional fourth argument, which is a map of options to pass to jetty, defaulting to {:port 8270, :join false?}.
To be clear, here is how you would start the server with these extra options (here, disabling the remote stopping functionality and changing the port for the server application):
(use 'robot-remote-server.core)
(server-start! (init-handler) false {:port 8888, :join? false})
Keywords can be word-separated using dashes or underscores, e.g. a RobotFramework keyword "Open Dialog" can be implemented as either the function "open-dialog" or "open_dialog". Avoid naming conflicts and stick to one method (dashes are more conventional for Clojure/Lisp; underscores are supported here for consistency with existing RobotFramework keyword libraries in other languages).
Any function with an asterisk * or exclamation-point/bang ! will not be included as a RobotFramework keyword, so if you absolutely need to put non-RobotFramework-keyword functions in your keyword namespace, include one of those symbols in the name. I highly recommend using an alternative namespace and requiring it separately.
If you're writing Clojure, you obviously have Java installed, so I recommend that you run your RobotFramework tests using the standalone jar that ships with RobotFramework. Check the downloads page for RobotFramework to find the latest standalone jar.
In addition, you need to add a Library statement to your RobotFramework tests *** Settings *** section to use this your Clojure keywords via the remote server:
Library Remote http://localhost:8270
After updating your test scripts with that setting, place the standalone RobotFramework jar in the same directory as your test scripts and run them as follows:
java -jar robotframework-x.x.x.jar my_robotframework_test.txt
There are a number of options you can pass to the jar; for more details, see the RobotFramework documentation on the subject. For a bare-bones example of a RobotFramework test, see the file resources/test.txt in this code base.
Thanks to Mark McGranaghan for his library ring, which makes defining the application handler and running it with Jetty a simple affair.
Thanks to Andrew Brehaut for his library necessary-evil and his help over IRC, which has made writing this XML-RPC server extremely straightforward.
Thanks to Michael Fogus for his library marginalia, which has been used to generate the beautifully-rendered source documentation available here.
Copyright (C) 2010 Daniel L. Gregoire (semperos)
Distributed under the Eclipse Public License, the same as Clojure.