Keynote - Preventing, Finding, and Fixing Bugs On a Time Budget | Raymond Hettinger @ PyBay2018

Channel:SF Python · Length:40:00 · Published:2018-09-21 · Views:27021

Watch on YouTube

Summary

Raymond Hettinger's PyBay 2018 keynote on preventing, finding and fixing bugs under a time budget. He covers testing practice, type annotation tradeoffs and the limits of coverage metrics.

Why HN recommends it

HN cites it in Python testing and code quality threads, including his point that 100% coverage proves little.

This is a good talk by the core developer Raymond Hettinger [1]. — HN, 2021

Python, Ruby & scripting languages · Testing, debugging & developer tools

Subtitles (excerpt)

[Music] this talk is on debugging and I was just debugging part of my little presentation that part doesn't look right and I thought well I'll just show you the regular screen on that one and I'll debug it later conference talk on debugging that has bugs in it so I have a notion of about testing tools is that it's basically they're all good everything that we've got that helps us find bugs in some way has some value which raises the question should you use all of the tools all of the time and the answer is probably not and because we have finite time constraints so this talk is going to be about what if you have a time budget are a time box how much testing and debugging can you get done in per unit of a time so I'm going to parade for you and demonstrate a number of tools that I've found to be really effective with your time some of them are practically instantaneous and they're so easy to use that if you don't use them you would be a fool and I'll show you some code that I wrote for myself not for other people and how it fits into my development process and I hope my sharing that with you can improve your life a little bit and that you might give these tools a try if you have a favorite testing and debugging tool that is not on

On Hacker News

This is a good talk by the core developer Raymond Hettinger [1]. He prefers pytest too. I don't do any crazy testing, but I really like property-based testing with Hypothesis, which is also mentioned. This video isn't Python but it's a great intro to property-based testing [2]. 1. [VIDEO] 2. [LINK] — Rendello, 2021-03
Please see Raymond Hettinger's keynote on efficiently handling bugs[0]. He makes the case that static type checking is a boon for Python except for in specific programs that make extensive use of covariant and/or contravariant types. [0] [VIDEO] — TrickardRixx, 2022-12
My examples are just personal anecdotes, you can dismiss them by saying "our team won't make the same mistake". If your goal is 100% coverage then it will turn testing into ritual and only give you the illusion of quality. Instead of testing inputs and edge cases, you will focus on testing lines of code. There's a good illustration of uselessness of 100% coverage in one of Raymond Hettinger talks… — hbrn, 2022-12
I had a similar experience after watching a Computerphile video with John Hughes, one of the authors of the original propert-based testing tool, QuickCheck [1]. Running hundreds of thousands of unique tests and finding the simplified cases was mind blowing to watch. I loved the video but my first experience with this method was with Python's Hypotheis [2], I haven't used it a ton but it's great f… — Rendello, 2021-04
Yes, they are probably most useful to me for the IDE completions and docs as well. Raymond Hettinger gave at least one talk [1] where he discussed how there are tradeoffs: reasons why you might use them and reasons why you might not. At the end of the day you can pass whatever you want to a function and the only reason to use types if they make your code better—but there are other tools that migh… — memco, 2020-12

Related videos