1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
[](https://github.com/robotology/robot-testing-framework/tags)
[](http://robotology.github.io/robot-testing-framework/index.html)
[](https://travis-ci.org/robotology/robot-testing-framework)
[](https://coveralls.io/github/robotology/robot-testing-framework?branch=master)
[](http://robotology.github.io/robot-testing-framework/documentation/robottestingframework_plugin_example.html)
[](https://github.com/robotology/robot-testing-framework/tree/master/examples/ada-plugin)
[](http://robotology.github.io/robot-testing-framework/documentation/robottestingframework_python_plugin_example.html)
[](http://robotology.github.io/robot-testing-framework/documentation/robottestingframework_ruby_plugin_example.html)
[](http://robotology.github.io/robot-testing-framework/documentation/robottestingframework_lua_plugin_example.html)
Robot Testing Framework
=======================
Robot Testing Framework is a generic and multi-platform testing framework for
the [test driven development (TDD)](https://en.wikipedia.org/wiki/Test-driven_development)
which is initially designed for the robotic systems.
However, it can be used for any TDD system.
The framework provides functionalities for developing and running unit tests in
a language and middleware independent manner. The test cases are developed as
independent plug-ins (i.e., using scripting languages or built as dynamically
loadable libraries) to be loaded and executed by an automated test runner.
Moreover, a fixture manager prepares the setup (e.g., running robot interfaces,
simulator) and actively monitors that all the requirements for running the tests
are satisfied during the execution of the tests.
These functionalities along with other facilities such as the test result
collector, result formatter and remote interface allow for rapid development of
test units to cover different levels of system testing (see the block diagram).
Installation
------------
Robot Testing Framework library does not depend on any external library.
The Robot Testing Framework framework has a robottestingframework-testrunner
utility (see Running test case plug-ins using robottestingframework-testrunner)
to easily run the test cases which are built as plug-ins.
Test cases can be organized in test suites using simple XML files.
The robottestingframework-testrunner uses TinyXml library for parsing the suite
XML files.
Robot Testing Framework build system check for the installation of TinyXml and,
in case, it cannot find any installed version of TinyXml library, it uses the
internal version which is delivered with the Robot Testing Framework.
- **On Linux/Mac:** The installation is easy, straightforward and uses the CMake
build system.
```
$ git clone https://github.com/robotology/robot-testing-framework.git
$ cd robot-testing-framework
$ mkdir build; cd build
$ cmake ../; make
$ make install # Optional!
```
- **On Windows:** The installation is easy, straightforward and uses the CMake
build system.
Get [CMake for windows](https://cmake.org/download/) if you have not yet
installed.
Then simply run the CMake and, set the project (robot-testing-framework) root
folder and the desired build folder.
Configure and generate project solution for your favorite IDE (e.g. Visual
Studio 17).
Then open the solution from your IDE and build the project.
Configuration
-------------
The only thing you need to configure is the `RobotTestingFramework_DIR`
environment variable so that CMake can find Robot Testing Framework libraries
and header files.
- on Linux/Mac:
```
$ echo 'export RobotTestingFramework_DIR=<path to the Robot Testing Framework build director>' >> ~/.bashrc
$ echo 'export PATH=$PATH:$RobotTestingFramework_DIR/bin' >> ~/.bashrc
```
- on Windows:
```
C:\> setx.exe RobotTestingFramework_DIR "<path to the Robot Testing Framework build director>"
C:\> setx.exe PATH "%PATH%;%RobotTestingFramework_DIR%/<Release/Debug>/bin"
```
*Notice:* If you have **not** installed Robot Testing Framework in the standard
system path (e.g., on Linux without `make install`) then You need to expand your
system `PATH` environment variable.
Enabling Python, Ruby, Lua, ... Plugins
----------------------------------------
To use Robot Testing Framework with other languages,
- first you need to install their development packages (e.g. for Python on
Linux you need `python-dev`, for Ruby: `ruby-dev` or for
Lua: `liblua5.x-dev`).
- then you can enable the desired language into Robot Testing Framework CMake
(e.g. `ENABLE_PYTHON_PLUGIN=ON` for enabling python)
- compile and build Robot Testing Framework
Tutorials and Examples
-----------------------
* [*Some example codes for using Robot Testing Framework classes.*]( http://robotology.gitlab.io/docs/rtf/master/examples.html)
* [*Using plug-in to develop test cases.*](http://robotology.gitlab.io/docs/rtf/master/robottestingframework_plugin_example.html)
* [*Using Lua plug-in to develop test cases.*](http://robotology.gitlab.io/docs/rtf/master/robottestingframework_lua_plugin_example.html)
* [*Using Python plug-in to develop test cases.*](http://robotology.gitlab.io/docs/rtf/master/robottestingframework_python_plugin_example.html)
* [*Using Ruby plug-in to develop test cases.*](http://robotology.gitlab.io/docs/rtf/master/robottestingframework_ruby_plugin_example.html)
* [*Running test case plug-ins using robottestingframework-testrunner*](http://robotology.gitlab.io/docs/rtf/master/robottestingframework-testrunner.html)
Documentation
-------------
* [*See Doxygen generated documentation*](http://robotology.gitlab.io/docs/rtf/master/index.html)
* [*See Robot Testing Framework website*](http://robotology.github.io/robot-testing-framework/index.html)
Authors
-------
* Ali Paikan ([*personal page*](http://alipaikan.com))
* Silvio Traversaro ([*personal page*](http://www.iit.it/en/people/silvio-traversaro.html))
* Lorenzo Natale ([*personal page*](http://nat.liralab.it/))
|
