[TIP] structure of a testing talk

andrea crotti andrea.crotti.0 at gmail.com
Tue Oct 2 05:24:51 PDT 2012

2012/10/2 andrea crotti <andrea.crotti.0 at gmail.com>:
> 2012/10/2 Ned Batchelder <ned at nedbatchelder.com>:
>> Andrea, this is helpful to me.  I've proposed a Getting Started Testing
>> tutorial for PyCon, and it's great to see how other people tell the story.
>> My tutorial is an expansion of a talk I did last year at Boston Python.  You
>> can see my slides from that talk at
>> http://nedbatchelder.com/text/starttest.html .  I'll accept tweaks to my
>> story line too!
>> --Ned.

Another couple of things which I think are useful and I didn't see are:
- pure functions and side effects

- why in Python it's even more important than other languages to test
  (I'm speaking to C programmers mainly here, so might depend on the
  audience). And maybe some examples of how things can go horribly
  wrong only at run-time even if there was a clear big mistake in the

Apart from that I might steal many ideas, but I only have until Friday to
prepare the talk, so I won't be able to explain everything..

Another thing which I will do is to use IPython+Emacs a lot, to show
actual live code.

And about this a nice little project from PyconUK might also be
useful.  This allows you to replay code that you already wrote in an
interpreter, in a presentation style, avoid typing but keeps the talk
interactive at the same time:


More information about the testing-in-python mailing list