Skip to content

Testing Procedures

amessing edited this page May 18, 2016 · 1 revision

Weekly Testing

Each week (or as applicable), we plan to perform some system tests to identify any regressions (new bugs) in the code base. Additionally, this serves as an opportunity to perform integration testing which verifies the system works together as a single, cohesive unit.

The exact procedure for this is TBD and will likely evolve as we progress further with the robot's development.

Regression Testing

The idea behind regression testing is to periodically run a set of tests to help identify any new bugs introduced to the codebase. This is important because when a developer makes a change there may be unintended consequences which may go unnoticed for an extended period of time. This, in turn, makes identifying the issue much more difficult.

Integration Testing

Integration testing is used to verify the various components of an overall system work together in harmony as intended. As the robot is quite complex with multiple processors and subunits, it is essential for all of the components to work together.

Random Course Setup Utility

The course setup utility is now integrated into the robot status page at utk-robotics-2016.github.io. The full code is available in the website git repository. Using this tool, you can generate a new random course setup. This is simply for testing purposes.

Clone this wiki locally