[ros-users] [Discourse.ros.org] [Quality Assurance] Design By Contract

Asmodehn ros.discourse at gmail.com
Thu Feb 15 12:01:24 UTC 2018

[quote="gbiggs, post:43, topic:2405"]
Making it easy to see where an error originated could go a long way to helping integrators find nodes with quality problems so those can be reported. This means making it more obvious why a node process died, for example.

We already discussed the idea of having a "chaos node" sending random message ( with a content following the message format ) to existing topics and services, which helps discovering "unsafe nodes" during development.

But here I notice your focus on post-mortem analysis on "systems in production". Maybe we could parametrize the "chaos node" to be able to run it in production, just like server farms run some potentially destructive tests in production, but when there is a low demand ?

Post mortem also mean, the system is running in production, but crashes and we want to know what happens. I am not aware of any tools for this purpose yet... Each node can use the tools of the programming language it was written in, but as for the communication between nodes, maybe we should have a library bagging each message, and keeping it for a certain amount of time ? some instrumentation that node writer could add to their code, so that when one node crash, we can get the log of all messages received (and sent) by that node ? 

Is anyone aware of such a lib/module, or maybe it s just an extra feature we can add to existing core ROS libs ?

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

More information about the ros-users mailing list