This Wednesday the 20th, I’m speaking at the Boston Python Meetup: Getting Started Testing your Python. Please do come if you’re in town. My goal will be to provide a totally from-scratch introduction to how to test Python code, in two hours, with time for questions.
I think I may have too much to say, though. The presentation itself is available for review. It could use another (hundred) pair of eyes. If you have any suggestions about what I should leave out, what I need to add in, what I’ve done completely wrong, and so on, let me know, either in a comment here, or in an email.
How do you reason your decision?
Is there any chance your talk will be taped? I'd love to show it at work -- either that or give the talk using your slides (assuming that's okay with you).
A related coverage.py question: I like nose, but don't like to pull in dependencies unless I really have to. Now that Python 2.7/3.2 unittest has discovery built in I plan on using it instead. How does one run coverage.py when using the unittest test discovery?
PS. Slide 66 ('It works great!') has bullet points but no text. Missing content?
And wow, this mocking via shadowing the system call in #70 makes me really jealous, that's not working in many languages I use. Would be so convenient...
URL on last slide is also a bit too wide.
Thanks for sharing :)
About unittest in 2.7: You discover tests with "python -m unittest discover", so you can simply replace "python" there and use: "coverage run -m unittest discover".
Slide 66 indeed was unfinished, thanks.
Add a comment: