Tools for Better Testing for Open Source Projects
summary
OpenStack QA implements a Gerrit-driven check and gate pipeline that blocks merges until tests pass, using Jenkins and nodepool to run about 12,000 jobs daily across environments. Test environments are built with devstack, functional suites run via tempest, results go through subunit into a MySQL store and visual dashboards, and elastic-recheck fingerprints known failures to flag flakes. The system catches regressions pre-merge and makes upstream QA repeatable and measurable.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:54Meet Dong Ma
- 2:20Agenda
- 3:03What is QA
- 8:07OpenStack CI
- 11:38Carrot
- 16:42Most important tools
- 17:18Devstack
- 19:20Tempest
- 20:41OpenStack Health
- 23:18Subunit Circle
- 24:18Elastic Recheck
- 25:30VOCs
- 26:09Stackbase
- 26:58Demo
- 28:51Test Results Dashboard
- 30:07Tips
- 31:46Conclusion
related talks
54mOpenStack Development: The Infrastructure Behind the Infrastructure
24mBetter Testing Through Statistics
33mOpenStack Compute's automated testing
30mQA in DevOps: Transformation thru Automation via Jenkins
36mFrom Sledgehammer to Fine Brush for QA
38mopenQA - end to end testing of operating systems
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
26mLAVA + OpenQA = Automated, Continuous Full System Testing