TDD (Test Driven Development) started from Test First Programming, and has been around at least since the 90's.
However, software tools and available CI systems have changed quite a bit since then.
Maybe it's time to re-examine the assumptions, practices, processes, and principles of TDD.
At least in the context of my software engineering career, modifications to TDD, at least the version of TDD as it's frequently taught, have been necessary.
This is the start of a series focused on examining TDD and related lightweight practices and processes.
Links from the show:
Thank you Coverage Cat for sponsoring this episode
161: Waste in Software Development
160: DRY, WET, DAMP, AHA, and removing duplication from production code and test code
159: Python, pandas, and Twitter Analytics - Matt Harrison
158: TDD in Swift - Gio
157: pre-commit - Anthony Sottile
156: Flake8: Python linting framework with Pyflakes, pycodestyle, McCabe, and more - Anthony Sottile
155: Four Questions to Ask Frequently During Software Projects - Tim Ottinger
154: Don't Mock your Database - Jeff Triplett
153: Playwright for Python: end to end testing of web apps - Ryan Howard
152: Python Packaging - Brett Cannon
151: Python Adventure - Brandon Rhodes
150: A Practical Testing Strategy
149: I don't test my code, "crappy Python" is all I write - Corey Quinn
148: Coverage.py and testing packages
147: Testing Single File Python Applications/Scripts with pytest and coverage
146: Automation Tools for Web App and API Development and Maintenance - Michael Kennedy
145: For Those About to Mock - Michael Foord
144: TDD in Science - Martin Héroux
143: pytest markers - Anthony Sottile
142: MongoDB - Mark Smith
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast