Lightning Talk: Automation and Process to Increase Code Quality
summary
A 45,000‑line C++ library moves from about 40% test coverage to a target near 80% while eliminating roughly ~1,000 warnings, enforcing warnings-as-errors, and gating merges with CI. Automation uses Travis and github actions for test runs, coverage measurement and static analysis, with coverage uploads to a coverage service. Plans add more static analyzers and sanitizers and a team C++ QA best practices doc so the repo refuses merges until checks pass.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:31Github
- 0:46How it started
- 1:48First step
- 2:27Second step
- 3:18Tools
- 4:05Next Steps
- 4:26Conclusion
related talks
01h 01mA Test a Day Keeps Your Manager Away!
07mLightning Talk: Shift Left With AI: Smarter Code Reviews for DevOps...
26mStatic Code Analysis with Gitlab CI
32mBuilding Confidence Together: Continuous Integration & Testing
40mAutomate All The Things!
06mLightning Talk: DevSecOps for C++? Keep Calm and use Conan
05mSet it and forget it!
30mFrom Chaos to Quality: Elevating LitmusChaos with CI/CD and Pull R...