Skip to content

4. testing

Verna Koskinen edited this page Dec 17, 2015 · 1 revision

The robot should be tested in approppriate level of comprehension. You do not need automated tests (but are also not discouraged to build some), but if your project contains for example algorithms you have made your self, it would be wise to unit test them. Testing different use cases might be more meaningfull to do by hand and document their results carefully. Without any documentation on what has been tested and how, you will get no points for testing.

Example

If your robot is a remote controlled car, which can automatically stop when facing a barrier, you could test at least the following conditions:

  • Which is the minimum height of the barrier that the robot can detect?
  • What if the barrier is skewed from the direction the robot is moving?
  • Does the emergency stop work every time?
  • What will the robot do when connection to the driver is lost?

It's most meaningfull to test the normal behaviour of the robot and borderline cases for it!

Clone this wiki locally