Road Runner Validation Tests
Use straight, turn, and spline tests to verify readiness.
Module 12: Road Runner 1.0 Setup and TuningRoad Runner
FTC · Java
In this lesson, you will:
- 01Validate simple motions.
- 02Run SplineTest last.
- 03Separate tuning from path design.
Concept narrative
Validation proves the robot model is good enough for autonomous planning. It should happen before students spend hours designing paths.
Robot mental model
Simple tests isolate basic behavior. A spline test is meaningful only after straight motion, turning, and localization are already believable.
Implementation walkthrough
Run short line tests, turn tests, repeated back-and-forth tests, then SplineTest. Log errors and decide whether to retune or redesign.
ValidationChecklist.javaJava
// 1. short line
// 2. turn in place
// 3. repeat forward/back
// 4. spline validation
telemetry.addLine("Record result before changing constants");Common mistakes and debugging
If spline fails but straight and turn tests pass, inspect path constraints and localization. If straight fails, return to tuning rather than editing path shape.
Checkpoint
- Tests run in order.
- Failures are categorized.
- No complex auto before validation.
- The test record includes the setup, prediction, and observed result.
- A teammate can repeat the check from the saved evidence without guessing.
Reflection check
Check your understanding before moving on.
Which result best demonstrates completion of “Road Runner Validation Tests”?
Why record the test setup, prediction, and observed result?
0 of 2 answered
References
Finished reading?
Mark this lesson complete — “Action Builder and Trajectories” is up next.