-
Notifications
You must be signed in to change notification settings - Fork 0
Testing
Max Krieger edited this page Sep 3, 2016
·
6 revisions
Every component we write should be categorically unit testable. This is inherently necessary in the code if you extends Component
.
That means we should be able to test every bit of functionality on the robot quickly and efficiently.
##The Ideal Testing Setup
The ideal testing setup involves running an opmode which outputs like so:
[✓] Motor 1 functional.
[✓] Motor 2 functional.
EXCEPTION: could not find motor "m3"
[×] Motor 3 NONFUNCTIONAL.
By doing this, we can catch errors early and often. We can also see every part of the robot at work.
##The Test Selector
The test selector opmode allows for easy testing of Organs. One can use the joystick and A1
controls to select an organ from the onscreen menu and test it, respectively.