While it seems less valuable to emulate Arduino in a CI/CD setup, are there any experiences/best practices for collaborative teams to automate their acceptance tests where a real Arduino is integrated into a CI/CD toolchain (or, what are comparable practices)?

Minimal example of acceptance testing:

  • compilation is successful for a given compiler version.
  • Step one: Define what acceptance means in your project workflow.
    – Majenko
    Apr 9, 2020 at 10:15
  • added a minimal example.
    – J. Doe
    Apr 9, 2020 at 10:17
  • For that: run arduino-builder in a script run by a cron job.
    – Majenko
    Apr 9, 2020 at 10:21

1 Answer 1


There are different approaches around. I can only point you to some of them:

As a valuable commenter mentioned on your previous question - this does not cover the attached hardware testing (sensors/ motors) - this has to be "integrated" via a test lab station, which you have to control manually (or semi-automated via lab equipment) on defined release/version changes

  • thank you so much @Codebreaker007! Trying out approach A to compile the controller code for an open source ventilator project :-)
    – J. Doe
    Apr 9, 2020 at 11:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.