![]() Hence, it is far more valuable and efficient to write unit tests that do not run on the target device (or emulator).įrequent testing on your target hardware has a painfully slow cycle: Think about it this way: Even if you were to test functionality of the Arduino library, the microcontroller hardware, or an emulator, it is absolutely impossible for such test results to tell you anything about the quality of your own work. ![]() Unit tests should generally never test the functionality of factors outside of your control. The purpose of unit testing is to test the quality of your own code. To be much smaller than the whole project. I am trying to make a point about optimizing yourĭevelopment feedback cycle by eliminating your target hardware from Telling you to avoid all practical testing on your ultimate target ![]() Really trying to make an argument about that here. ![]() There's a lot of discussion about what unit test means and I'm not Don't Run Unit Tests on the Arduino Device or Emulator The case against microcontroller Device/Emulator/Sim-based tests ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |