For some years I have been using test-driven development (TDD) to good effect in my career, which is writing software that runs on "full" computers. The learning curve is steep, but it makes code so much easier to develop and maintain that I can't see a reason to go back to the old way.
Well, maybe one reason, where Arduino-based stuff is concerned: I don't know if it can be done. There is a lot of stuff like delayMicroseconds() that isn't in a standard libc, so I don't know how it would compile for my dev machine.
Obviously, I can't test things like interrupts and GPIO on an x86-64 target, but the majority of code is at a higher level of abstraction and could be unit-tested, if only it could be made to compile.
Anyone have any luck with this?
Well, maybe one reason, where Arduino-based stuff is concerned: I don't know if it can be done. There is a lot of stuff like delayMicroseconds() that isn't in a standard libc, so I don't know how it would compile for my dev machine.
Obviously, I can't test things like interrupts and GPIO on an x86-64 target, but the majority of code is at a higher level of abstraction and could be unit-tested, if only it could be made to compile.
Anyone have any luck with this?