Author(s):	Thomi Richards
Location	Track 2
Date	sep Sat 13	Days Raw Files
Start	11:20	First Raw Start	error-in-template
Duration	00:30:00	Offset	None
End	11:50	Last Raw End
Chapters
Total cuts_time	None min.

https://kiwi.pycon.org/schedule/presentation/59/
raw-playlist raw-mp4-playlist encoded-files-playlist host public mp4 svg png

assets release.pdf A_Testing_Talk.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:	= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Thomi Richards: A Testing Talk = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = @ Kiwi PyCon 2014 - Saturday, 13 Sep 2014 - Track 2 http://kiwi.pycon.org/ **Audience level** Intermediate **Description** This talk will contain my opinionated views on several topics, including, but not limited to: - Which areas of testing are well catered for, and which are not? - What sources of bugs are frequent, and very hard to test? - Should we perhaps start talking about unit tests less, and start talking about other forms of testing more? **Abstract** In my day job I spend a lot of time looking at projects that are part of Ubuntu, and trying to find out why they’re being released with bugs. This in turn leads to a lot of dissection of test suites, and a lot of discussion with my colleagues around tests, names of tests, why some tests are better than others, where the common gaps in test coverage are, how applications should be tested, where, when, and why certain test suites should be run, and other subjects too boring to mention. Having done this for several years, I've started to form a few troubling thoughts about the state of automated testing in software development, and in python specifically. When taken together, these can start to form a rough and ready 'testing philosophy' - a way of looking at code and, by analysing it's structure and visibility, start to find gaps in it's test coverage. This talk contains no silver bullets - no magical solutions, but does (hopefully) contain some interesting questions. **Slides** https://speakerdeck.com/nzpug/thomi-richards-a-testing-talk markdown
Comment:	production notes