Testing And Verification

Robo Buggy is a complex cyber physical system with many layers.

• Testing before software is marked as stable (ready for rolls):
1. push code to git hub have it pass all dynamic tests at https://travis-ci.org/[Travis]
2. push code to git hub have it pass all static tests at coverityhttp://www.coverity.com/
3. push code to git hub have it have full coverage with coverityhttp://www.coverity.com/
• Testing before buggy is certified for rolls
1. TODO
• Day of testing
1. Testing in Shop
• Check static mechanical stability of hardware
TODO detail test
• Testing at rolls (before free roll)
• Test brakes and steering at speed (push buggy fast on side walk, have it break after buggy stops release breaks and reapply them a few seconds later, effectively capes)
• Push buggy through Chute at speed
• test E stop at a random point along walk around
• walk the buggy around the course and ensure that the buggy behaves properly
• Run system test
• ensure GPS lock ( location is correct)
• ensure getting camera feed from all three webcams
• ensure encoders are reporting (spin wheel a set distance and see if it matches predicted
• ensure IMU is reporting (turn buggy 180 degrees and ensure that values match)
• Check lights
• Check Servo goes to desired locations