Quote:
|
Originally Posted by scitobor 617
What exactly is the role of the tester? I normally test as I write.
|
So, I just wrote some new driving code. It has three modes of operation: pivot in place, go straight, or arc. Ideally, I write up the code, and someone reads through it to make sure that it makes sense. Then I compile it, and send it to the RC. Another person hooks up the OI, and tests the various operations to make sure that it works as intended, and that the controls are manageable. (When coding a control system, it often makes sense in your head, but comes out far too sensitive for the drivers.) Robot programming is not like computer programming, where you can instantly test little parts of code with some printf (or cout, or System.out.println, depending on your favorite flavor) commands on a console window. I've found that it's much more efficient to write large things all at once, because it's very time-consuming to compile the code, power up the robot, download the code with IFI Loader, and test the code. That's why it's nice to have someone else around to take over the whole process.