Automating Code Quality
summary
Automates manual review steps by wiring flake8, pylint, and coverage into a local dev workflow and CI so commits must pass a make PR check before merge; shows using requirements-dev.txt, a Makefile, Travis jobs for multiple Python versions, and Codecov to block coverage regressions. Demonstrates concrete fixes (PEP8, default mutable args, McCabe complexity) and reports numbers like coverage percentages dropping when branch coverage is enabled.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:35Automating Code Quality
- 0:54Standards
- 1:43Safe Practices
- 2:39Open Source Projects
- 3:13Chalice
- 3:55Quality Checks
- 4:24Code Review
- 5:29Safety Net
- 6:02Steps
- 10:25Pilot
- 14:50Coverage
- 15:09Pytest Cove
- 16:34HTML Report
- 16:52Recap
- 18:49Making it easy to run
- 21:20PR Check
- 23:16Benefits
- 24:20Best Practices
- 25:22Avoid compromising existing checks
- 26:11Do thorough code reviews
- 28:53Outro
related talks
40mCode Review Skills for Pythonistas
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
25mcode review is too late for code quality
23mDrama-Free Code Review!
29mManaging the code quality of your project. Leave the past behind: Focus on new code.
36mContinuous Integration For The Win!
41mCracking the Code Review from Guesswork to Automated Guidance
21mMaking the Most Out of Code Reviews