Ned Batchelder: Getting Started Testing - PyCon 2014

Speaker: Ned Batchelder
If you've never written tests before, you probably know you *should*, but view the whole process as a bureaucratic paperwork nightmare to check off on your ready-to-ship checklist. This is the wrong way to approach testing. Tests are a solution to a problem that is important to you: does my code work? I'll show how Python tests are written, and why.
Slides can be found at: speakerdeck.co... and github.com/PyC...

[@nikoachtzehn4776]

This is among the most useful Python talks I heard so far. That was a lot of content!

[@xxxdnaskatexxx]

I agree 100%

[@RachelKelly]

LOVE the intro to testing - see, you can do it yourself, comprehensably! And now let's move to unittest which takes care of so many of things for you. So clear.

[@NoTengoIdeaGuey]

Ned Batchelder is without a doubt one of the best speakers at any Pycon ever. Lots of people have good info in their talks but no one has quite the ability to speak their part in quite a clear and concise way. No corny jokes, no rote reading of the slides one after the other, no awkward pausing or stammering, dank info throughout.

[@sntshkmr60]

Pro Tip at 17:18 was really helpful.

[@muditjain7667]

How does he do the highlighting of his code lines? Is it pre-programmed or someone manually helping him?

[@WSebastiaanZ]

From what I can see: everything is preprogrammed. He has a presenter tool in his right hand and most presenter tools have a back button (usually just registered as a "page up" key press) and a forward button ("page down"). If you watch closely, you'll see that he goes through all the lines in a code block sequentially*. If he wants to go back, he just presses back; if he wants to go forward in the code he just presses forward. To advance to the next slide, he just presses forward until he reaches the end of the code block (or the predetermined endpoint after which he doesn't want to highlight) and then the next press will transition the slide show to the next slide. This seems very smooth because he's a very professional and well-prepared speaker. He knows what he wants to talk about and his slides are very structured. That means he never has to skip over a lot of lines just to get to the lines he wants to highlight or to the transition point to the next slide; the structure of his slides (and code) make it so that it all flows very naturally. He's a really good speaker IMO and I really enjoy watching his talks. *) Of course, he can select the lines he wants to be able to highlight in the first place; it doesn't have to be the whole code block.

[@arkster00]

Just watched this again. Ned's one of my favorite pycon speakers. Thanks again for the content that is clear, concise, to the point with the great q and a.

[@bernardoamorim9495]

Is the tear down method shown @ 28:14 really necessary? If so, why?

[@bernardoamorim9495]

OK, thanks, dude!

[@Gaurav-S]

Thank you for putting up such a great talk. You explained the concepts in such a good fashion by building one on top of another. Really helpful.

[@EmadGohari]

This was really useful talk. I wish it went deeper into those other topics.

[@wadsonespindola]

Clear and Concise intro to Unit Testing in Python. Kudos!!!

[@benjamin_rr]

Brilliant session on testing, definitely worth a watch!

[@Jarihopkins]

Didn't know Al di meola can code! Cool!

[@psypher514]

throw more dots. more dots. more dots.

[@asmarinodude]

awesome presentation!

[@ivecrs1929]

nice