Six QA Tools that will make your Python code better
summary
Case study applies six specific tools — Black iSort PyLint MyPy PyTest Coverage — to real AEMO code, showing concrete fixes: string-sorted numbers, trailing-comma tuple, and attribute-typo bugs get caught by formatting, linting, typing, tests and coverage. Code is refactored into entry/tests/data/behavior to enable pytest, and a policy enforces 100% coverage requirement before production. Project stats: 71,000 lines of production, 52,000 lines of tests (≈40%), and QA can consume ~45% of dev budget but yields reliably safer deployments.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:19Trivial bugs in Python
- 7:12Are you done?
- 7:55Six QA tools
- 8:16Sort cleans imports
- 8:59Black formatting
- 10:43Pylint catches errors and enforces standards
- 14:37Pylint for new coders
- 16:02MyPy static checks
- 17:08Pytest tests code
- 21:49Coverage improves tests
- 24:55100% coverage needed
- 26:40Definition of done
- 27:01Q&A
