Define test platforms

[rhauch]

Define a series of one or more test platforms that Strongback collaborators can use to verify that Strongback code works correctly on real hardware.

Each test platform would be described by a thorough design (e.g., CAD models, part lists, assembly instructions, photos, etc.) and a specific robot codebase that uses Strongback. Teams volunteer to build the test platform per the specs, compile and deploy the robot code, run the tests, and share the results.

Ideally the test platforms would be fully-autonomous and closed-loop, meaning no user input is required to complete the tests and generate a report, and that all actuators are verified by multiple sensors. For example, a test platform that tests pneumatics might use multiple sensors (e.g., reed switches on the cylinder, proximity switches on the structure, etc.) to automatically verify that the solenoid retracted/extended. One goal would be to create a simple of a test platform that uses and verifies the largest number of components. Note that a test platform might not require a drive train.

It is unclear whether drive systems, accelerometers, and gyroscopes can be tested this way. If so, maybe the test needs to be performed in a large room so the robot can move around autonomously. If that's too dangerous, then perhaps those tests need to be tele-operated.