[ros-users] [Discourse.ros.org] [Next Generation ROS] Design By Contract

Asmodehn ros.discourse at gmail.com
Sun Oct 8 13:21:13 UTC 2017

Quick replies : 
- pyros-test is MIT or BSD, along these lines, I just haven't taken the time to put a file there... I ll try to do it soon.
- python makes things simpler than C++ as there are defacto standard test frameworks. So I am trying to support whatever basic python and ROS support ( unittest, doctest, and nose ) and pytest. unittest already includes a mock library by the way in python3, which is just the mock library in python2 .
- pyros-test is currently very very simple (probably too simple to need a separate package), and I'd like to eventually improve it when I get the chance... 

But IMHO you re probably better of extracting what I already started in https://github.com/pyros-dev/pyros-msgs and https://github.com/pyros-dev/pyros-schemas : have a look at property based testing and [hypothesis](http://hypothesis.works/), it should be simple enough to automatically generate fake nodes based on an existing message definition and then send fake messages around :-) .

Some example of hypothesis use here : https://github.com/pyros-dev/pyros-schemas/blob/nested_merged/tests/test_pyros_schemas/hypothesis_example.py and an example of generating messages with it there https://github.com/pyros-dev/pyros-schemas/blob/nested_merged/tests/test_pyros_schemas/test_basic_fields.py

By the way, roschaos looks fun, and there is probably a clever way to integrate it with roslaunch or feed it launch/test files... I ll play with it when I get some time.

[Visit Topic](https://discourse.ros.org/t/design-by-contract/2405/27) or reply to this email to respond.

More information about the ros-users mailing list