Quote:
Originally Posted by Greg McKaskle
I think this is a good summary looking to the future. The thing that could probably be stated more directly would be to allow programming to proceed without the robot. In my book that means test harnesses so that code logic can be validated more quickly and more safely somewhat independent of the robot. After all, NASA rarely launches another rocket just so the programmers can see if they've fixed a bug.
|
Agreed. The most frustrating thing for me last year at the beginning of the season was the fact that the C++ stuff *had* to be run on the robot, and so it made it really annoying to do anything really significant to the code without any *easy* way to test it. In particular, I don't have 24/7 access to the facility where our team has the robot, so most of the coding I did last year I ended up doing at home, because we simply don't have enough time to do it in the time we meet at the school -- and I can't bring the robot home!
I ended up building a reasonably nice GUI test harness for WPILib/C++ that allows you to run your robot program on a desktop (Windows or Linux) and stimulate various inputs and view the outputs. More information and download links at:
http://www.virtualroadside.com/blog/...ness-released/.