OpenStack Compute's automated testing
summary
Patch approval triggers Jenkins which pulls approved patches from Launchpad, applies them, runs unit tests and a PEP8 pep check, and posts test output back to Launchpad; passing patches increment the repo version early, build docs, create a tarball, apply Debian packaging and upload source packages to PPAs. Integration tests then run on four Ubuntu releases and on four farm servers that boot, attach volumes and destroy instances, so packaging comes from the tarball not the VCS to keep releases reproducible. build packages from the tarball automated gate that rejects failures
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09What is OpenStack
- 3:23Quality assurance challenges
- 5:11Patch review process
- 8:04Automated testing with Jenkins and Tempest
- 10:11Additional automated checks
- 13:12Preventing broken trunk
- 15:26Automated release process
- 20:40Delta checks and integrity
- 22:52Building packages
- 25:01Multi-platform package testing
- 26:45Reference server tests
- 28:08Future testing plans
- 29:15Summary
- 29:44Q&A
related talks
32mTools for Better Testing for Open Source Projects
24mBetter Testing Through Statistics
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
24mWill it Run on *My* OpenStack? – Building an Executable Validation Testsuite for CPIs
41mBeyond unit tests
19mUpstream kernel CI using patchew and TDC
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
30mWorks, so now what?