The 2012 TiPBoF
Shout Outs!
Paul Hildebrandt & DisneyHerokuJesse NollerEwa JodlowskaPeter Kropf
Thank YOU!
Let’s Start the Show
Top 10 Reasons No One Uses     Your Testing Tool.    The Python Testing Cabal
10. Your tool is for behavior driven development, which no one does.“BDD is a second-generation, outside-in, pull-  based,...
9. Your test tool requires inheritance  and use CamelCase, so everyone   thinks it’s actually for Java code.             C...
8. Your documentation sucks.“See examples for information on use.”
7. Your testing tool is only usable byprogrammers, and barely even them.“So, just instantiate the Frobnitz class, stick it...
6. Your own tests don’t work  Irony, thy name is open source.
5. Your tool runs tests so fast, they      can’tactually be doing anything.% bernhardtests……………………………………………….…………………………………...
4. Nobody can figure out which of your       assert functions to use.From  http://docs.python.org/library/unittest.html:  ...
3. Your testing tool is only for          Python3…      …which no one uses.
2. It’s another fucking mock library.              ‘nuff said.
1. Your tool is for Web testing, yet      doesn’t support JavaScript.“twill strives to be a complete implementation   of a...
Thanks to Terry!And apologies to @voidspace…
Upcoming SlideShare
Loading in …5
×

pycon 2012 tip bof -- intro slides

10,867 views
10,692 views

Published on

Published in: Technology
1 Comment
5 Likes
Statistics
Notes
No Downloads
Views
Total views
10,867
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
16
Comments
1
Likes
5
Embeds 0
No embeds

No notes for slide

pycon 2012 tip bof -- intro slides

  1. 1. The 2012 TiPBoF
  2. 2. Shout Outs!
  3. 3. Paul Hildebrandt & DisneyHerokuJesse NollerEwa JodlowskaPeter Kropf
  4. 4. Thank YOU!
  5. 5. Let’s Start the Show
  6. 6. Top 10 Reasons No One Uses Your Testing Tool. The Python Testing Cabal
  7. 7. 10. Your tool is for behavior driven development, which no one does.“BDD is a second-generation, outside-in, pull- based, multiple-stakeholder, multiple-scale, high-automation, agile methodology. It describes a cycle of interactions with well- defined outputs, resulting in the delivery of working, tested software that matters.” Wikipedia: Behavior Driven Development
  8. 8. 9. Your test tool requires inheritance and use CamelCase, so everyone thinks it’s actually for Java code. Cheap shot, I know.
  9. 9. 8. Your documentation sucks.“See examples for information on use.”
  10. 10. 7. Your testing tool is only usable byprogrammers, and barely even them.“So, just instantiate the Frobnitz class, stick it into your base metaclass hierarchy with dependency injection, and voila! Syntax- highlighted tracebacks!”
  11. 11. 6. Your own tests don’t work Irony, thy name is open source.
  12. 12. 5. Your tool runs tests so fast, they can’tactually be doing anything.% bernhardtests……………………………………………….……………………………………………….……………………………………………….……………………………………………….……………………………………………….……………………………………………….……………………………………………….---------------------------------------------------Ran 2500 test in 0.002sOK
  13. 13. 4. Nobody can figure out which of your assert functions to use.From http://docs.python.org/library/unittest.html: “(If you are already familiar with the basic concepts of testing, you might want to skip to the list of assert methods.)” e.g. self.assertThisAssertIsFalse()
  14. 14. 3. Your testing tool is only for Python3… …which no one uses.
  15. 15. 2. It’s another fucking mock library. ‘nuff said.
  16. 16. 1. Your tool is for Web testing, yet doesn’t support JavaScript.“twill strives to be a complete implementation of a Web browser, omitting only JavaScript support.”
  17. 17. Thanks to Terry!And apologies to @voidspace…

×