user65221: 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.


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

GitLab CI approach A
GitLab CI approach B
Your specific solution: To build pipelines for Arduino (although its Azure) but you can use this technique on Linux with Jenkins

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

65221: <p>While it seems <a href="https://arduino.stackexchange.com/questions/74772/can-i-emulate-arduino-in-a-headless-ci-cd-setup?noredirect=1#comment162856_74772">less valuable</a> 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)?</p>

<p>Minimal example of acceptance testing: </p>

<ul>
<li>compilation is successful for a given compiler version.</li>
</ul>
 64075: <p>There are different approaches around. I can only point you to some of them:</p>

<ul>
<li><a href="https://codeblog.dotsandbrackets.com/gitlab-ci-esp32-arduino/" rel="nofollow noreferrer">GitLab CI approach A</a></li>
<li><a href="https://dzone.com/articles/hands-on-iot-devops-day-3-gitlab-cicd" rel="nofollow noreferrer">GitLab CI approach B</a></li>
<li>Your specific solution: To build <a href="https://devblogs.microsoft.com/premier-developer/azure-devops-build-pipelines-for-arduino-microcontrollers/" rel="nofollow noreferrer">pipelines for Arduino</a> (although its Azure) but you can use this technique on <a href="https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins" rel="nofollow noreferrer">Linux with Jenkins</a></li>
</ul>

<p>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</p>
