Req 4e — Test, Record, Improve
Testing is where engineering becomes honest. A design sketch can look perfect. A finished robot can still drift left, miss a target, stall under load, or misread a sensor. That is why good builders do not ask, “Did it work once?” They ask, “How well does it work, and what does the evidence show?”
Test on purpose
A good test has a clear goal. Decide what you want to measure before you start.
Examples:
- Does the robot stop within the target zone?
- Does the arm lift the object every time?
- Does the sensor react at the right distance?
- Does the robot complete the task in the expected order?
Run the same test more than once. One lucky success is not enough to prove the design is reliable.
What to record in your notebook
Your notes should show what happened, not just whether you liked it.
Record:
- date of the test
- test setup
- what the robot was supposed to do
- what it actually did
- any measurements, counts, or observations
- what you changed before the next run
You should also include pictures or sketches of the finished robot. Those visuals help your counselor see the final design and understand the system you built.
Useful test notes
Write down enough detail to learn from each run
- Trial number and test condition
- Result: success, partial success, or failure
- Specific problem noticed
- Suspected cause
- Planned fix or next adjustment
Improvement ideas matter
The improvement section is not a penalty. It is proof that you are thinking like an engineer. Common improvements include:
- moving a sensor for better readings
- lowering the center of gravity for stability
- changing gear ratios for more torque or speed
- strengthening a weak frame section
- cleaning up wiring
- adjusting code thresholds or timing
In the next requirement, you will demonstrate the robot and share what you learned. The stronger your test notes are now, the easier that conversation will be.