Hi Buğra, thank you for sharing your suggestions & relevant keywords!
While I agree that spinning gazebo is a good idea, esp., for integration testing purposes, I'm coming from a robotics app developer's perspective where I'd like to borrow lightweight model-based testing approaches (e.g., medium.com/criteo-labs/detecting-t...) to potentially even decouple the robot application layer from the rest of the (build) system to allow rapid prototyping of behaviors. I definitely agree that all applications must be tested in a more proper simulation environment like gazbo (and with a real robot eventually) but was thinking about ways to reduce the prototyping cycle time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Buğra, thank you for sharing your suggestions & relevant keywords!
While I agree that spinning gazebo is a good idea, esp., for integration testing purposes, I'm coming from a robotics app developer's perspective where I'd like to borrow lightweight model-based testing approaches (e.g., medium.com/criteo-labs/detecting-t...) to potentially even decouple the robot application layer from the rest of the (build) system to allow rapid prototyping of behaviors. I definitely agree that all applications must be tested in a more proper simulation environment like gazbo (and with a real robot eventually) but was thinking about ways to reduce the prototyping cycle time.