The ability to configure test messages/response that a request to a topic/service would give, would be quite important for testing code that uses pyros.
Currently the client has to actually mess with the underlying ROS system to be able to test pyros and code depending on it.
Ideally it would be easy to test these separately :
pyros + ROS with direct pyros request (simulating clients call). Actually we can already do this with REST (rostful + pyros + ROS).
pyros clients + pyros + rosmock with configurable ROS system behavior (to simulate ROS system actual behavior)
Rough Idea : yaml file that specify the message type and content to be instanciated when request comes. A pyros client could then test against different prepared msg data values...
One problem : simulate dynamic behavior... => maybe simplified python (ROS?) code simulating the whole ROS underlying environment ? we need to find a way to KISS...
Maybe this idea can be unified with the "mock" concept ?
fkromer
commented
7 years ago
The ability to configure test messages/response that a request to a topic/service would give, would be quite important for testing code that uses pyros. Currently the client has to actually mess with the underlying ROS system to be able to test pyros and code depending on it.
Ideally it would be easy to test these separately :
Rough Idea : yaml file that specify the message type and content to be instanciated when request comes. A pyros client could then test against different prepared msg data values... One problem : simulate dynamic behavior... => maybe simplified python (ROS?) code simulating the whole ROS underlying environment ? we need to find a way to KISS...
Maybe this idea can be unified with the "mock" concept ?