0

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.
Improve this question
3
  • Step one: Define what acceptance means in your project workflow. Commented Apr 9, 2020 at 10:15
  • added a minimal example. Commented Apr 9, 2020 at 10:17
  • For that: run arduino-builder in a script run by a cron job. Commented Apr 9, 2020 at 10:21

1 Answer 1

Reset to default
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

Improve this answer
1
  • thank you so much @Codebreaker007! Trying out approach A to compile the controller code for an open source ventilator project :-) Commented Apr 9, 2020 at 11:32

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.