Mashing up py.test, coverage.py and ast.py to take TDD to a new level
summary
Claims a concrete speedup: a py.test plugin "testmon" that uses coverage.py to record per-test executed lines and ast.py to map lines to functions, builds a dependency matrix and selects only affected tests after each file change. The tool runs a demo that reduces minutes-long suites to interactive runs, handles helper functions and fixtures when exercised, shows gaps (data files, cross-language code, session-scoped assumptions) and reports that the approach works reliably on real projects.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:23EXECUTING TEST SUITE..
- 2:57Broken test suite
- 3:24Majority of code changes are local
- 3:48When the dependencies look like this
- 4:09Example "project" with a test suite in one file
- 10:22py.test plug-in
- 11:23Interesting aspect - crowdfunding
- 14:10Contacts
- 19:05subtract vs. test add
related talks
35mTurning test writing into a consistently brief and pleasant experience
29mAdopt-a-pytest
27mWhy I use py.test and maybe you should too
30mVisual Testing with PyCharm and pytest
15m"Linux Testing made better with DATA"
03h 02mdef test_crash_course_with_pytest()
59mTesting in Python
38mMutants to the rescue: How effective are your unit tests?