Skip to main content
Arduino

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • Other than passing it through Ino and avr-size? Commented Jan 16, 2015 at 17:01
  • @IgnacioVazquez-Abrams I don't mind which tools to use, but it should run automatically on some cloud hosting or continuous integration service. Commented Jan 16, 2015 at 17:03
  • 1
    Compiling binary size isn't that hard, but to do unit tests, you would have to structure your code in such a way that it is unit-testable, which is hard enough if you want to keep size small. Besides, you will need to run those test on a chip or in an emulator to get a test that is more or less reliable. Commented Jan 16, 2015 at 19:46
  • I found github.com/kyab/travis-test-arduino but its experimental and a comprehensive answer/tutorial as answer would be better. Commented Jan 18, 2015 at 16:58
  • 3
    The issue with this is it goes against the original purpose of continuous integration: it's meant to push changes and then have it automatically build and deploy within minutes. This allows your customers to get the latest features and fixes as they happen, instead of every two months. For Arduino it's just "cloud making sure it builds." For unit tests you might have to bypass the Arduino libraries to build functions and send example data over the "pins." Commented Jan 18, 2015 at 17:13