Tag Info

We called those the BIST : Built-In Self-Test. The main "customer" from our viewpoint was manufacturing. They needed a suite of tests that they could run to verify that the hardware coming off the end of the line was good. The development team was responsible for implementing the tests, manufacturing was responsible for defining and running the tests.

You say they're close to unit tests, and running on the device, but with most of the surrounding functionality disabled. So I'd call them unit tests. You've isolated as much as you can of the embedded device, and if you're testing each class and method in isolation with as much mocking and stubbing as possible, then they're unit tests. The fact you're ...

This may be completely useless for your specific situation but I have used something similar to this for a past project that required me to do an automated reliability test. http://hacknmod.com/hack/incredible-100-arduino-based-cnc-machine/ Replace the router with a stylus/finger analogue and code up your test patterns in Python. There was something in ...