Automated Testing using Travis and Shippable
summary
OpenDataPlane configures Travis for dense cross‑compile matrices and Shippable to run tests on real ARM hardware, validating builds across x86 and aarch64 and catching regressions before merge. CI runs a cron of 200+ tests across different compilers and configure options, uses caching to cut rebuild time, and adds native AArch64 hosts for functional validation. Performance tests are planned but some are disabled because virtual CI variability breaks timing; the existing setup proves cross‑architecture compatibility while revealing flaky timing-dependent cases. Travis for matrix builds and Shippable for bare-metal tests.
AI-written summary · about
chapters (8)
- 0:00Introduction to automated testing
- 2:24Travis CI overview and setup
- 5:20Test matrix and configurations
- 10:07Caching and dependency management
- 13:58Using Shippable for cross-platform tests
- 17:59Optimizing test execution time
- 22:47Performance testing challenges
- 27:07Q&A
related talks
10mNative Parity for Development & Testing of SOAFEE Software-Defined Vehicle
35mTest Harness: Continuous Testing on Hardware
11mBuilding a Test for Diverse Fleet of Platforms, How Hard That Could Be?
42mGit and Testing
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
10mAutomated testing of GNU Radio builds
01h 01mA Test a Day Keeps Your Manager Away!
56mTestOps at scale