Our CI/CD in Robot Testing at the Edge of Software and Hardware
summary
Describes a CI/CD pipeline for robot testing combining GitLab + Docker for builds and simulation, x86 unit tests for fast firmware checks, and Python pytest + Allure for higher-level tests. Explains the hardware stage using Debian packages and manual flashing because field robots lack remote deploy, and integration on cost‑aware benches built with Arduino-based test rigs and real motors, clarifying which steps are automated and which remain manual.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:34Software focus
- 5:43Robot construction
- 11:11CI/CD for robotics
- 15:56Code build and test
- 17:25Static analysis
- 18:06Artifact build
- 20:12Firmware release
- 21:37Unit tests Java C++
- 23:45Component testing tools
- 25:55Component simulation
- 30:10Hardware bench tests
- 35:26Real bench integration
- 39:46Optimizing tests
- 42:18Final pipeline
- 44:28Q&A
related talks
47mOur CI/CD in Robot Testing, on the Edge of Software and Hardware
44mHow We Deliver a Robot
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
38mAutomating and Managing an IoT Fleet Using Git
05mInnovating Testing: Embracing DevOps and AI Trends
39mRemove your Testing Bottleneck with CI/CD Pipelines
28mUnderstanding CI/CD in Networking Context
22mEmbedded Software Development Efficiency Improvement with Docker and Kubernetes