Author: pekka.klarck
Date: Sun Apr 19 12:44:22 2009
New Revision: 1913
Modified:
wiki/RemoteLibrary.wiki
Log:
hopefully the final cleanup
Modified: wiki/RemoteLibrary.wiki
==============================================================================
--- wiki/RemoteLibrary.wiki (original)
+++ wiki/RemoteLibrary.wiki Sun Apr 19 12:44:22 2009
@@ -7,12 +7,12 @@
The Remote library is one of the [TestLibraries standard libraries] but
totally
different than the others. It does not have any keywords of its own
but it works as a proxy between Robot Framework and actual test
-library implementations.
+library implementations elsewhere.
There are two main reasons for using the Remote library and the remote
library interface it provides:
- * It is possible to have actual libraries on different machines than
where Robot Framework is running. This allows interesting possibilities for
distributed testing.
+ * It is possible to have test libraries running on different machines
than where Robot Framework itself is executed. This allows interesting
possibilities for distributed testing.
* Test libraries can be implemented using any language that supports
[http://www.xmlrpc.com XML-RPC protocol]. Robot Framework currently
contains generic remote servers for Python/Jython and Ruby, and the plan is
to implement generic servers for other languages like Java and Perl in the
future.
The remote library interface is described in detail in the [UserGuide User
Guide].
@@ -20,10 +20,10 @@
links to the available remote servers and related examples.
The Remote library is new in Robot Framework 2.1. It is also
-compatible with 2.0.3 and 2.0.4 versions, but it needs to be installed
-separately with them.
+compatible with 2.0.3 and 2.0.4 versions but it needs to be installed
+separately.
-= Architecture =
+= High level architecture =
The Remote library interacts with actual library implementations
through remote servers, and the Remote library and servers communicate
@@ -55,7 +55,7 @@
== Trying out examples ==
If an example library and the associated remote server are downloaded
-to the same directory, the library can be started using one of the
following
+into same directory, the library can be started using one of the following
commands:
{{{
@@ -74,7 +74,7 @@
These examples will start the remote server so that it provides
keywords implemented in the example module. After the remote server is
-started, an example test case file can be executed using the familiar
+started, the example test case file can be executed using the familiar
`pybot` or `jybot` commands, possibly giving the port where the server
is listening as a variable:
@@ -83,5 +83,5 @@
jybot --variable PORT:7777 remote_tests.html
}}}
-The results should be the same regardless the example library or start-up
+The results should be the same regardless of the example library or
start-up
script used.
