Author(s):	Iwan Vosloo
Location	Tugela Room
Date	oct Thu 06	Days Raw Files
Start	15:30	First Raw Start	error-in-template
Duration	00:45:00	Offset	None
End	16:15	Last Raw End
Chapters
Total cuts_time	None min.

https://za.pycon.org/talks/26/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Experiments_with_test_setup.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Ever since test driven development took hold, people have been experimenting with different ways to deal with setting up and tearing down test objects and data (amongst other things). Focussing on this particular concern (set up and tear down of test objects), this talk provides an overview of how the mainstream python tools have developed over time in this regard: unittest, nose and py.test. A bit of a wider context is also given in terms of two ideas pioneered by tools in other languages: the annotations of TestNG and resources of Smalltalk's SUnit. Two ideas that address problems beyond the reach of the tools themselves are also introduced, namely the "object mother" and "builder pattern". Against the backdrop of this overview, I also show some of our own experiments (as part of [the Reahl project](http://www.reahl.org)) to translate a combination of the object mother and the builder pattern into Python -- with surprising results. The talk is aimed at people interested in improving the ways we can do set up for tests and people who are generally interested in how tests can be made easier to write and more useful. I hope to stimulate more thoughts around the topic against the backdrop of a slight overview. The talk is accessible to newcomers to this topic as well. markdown
Comment:	production notes