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, 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

9. Your test tool requires inheritance and use CamelCase, so everyone thinks it’s actually for Java code.

Cheap shot, I know.

8. Your documentation sucks.

“See examples for information on use.”

7. Your testing tool is only usable by programmers, 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!”

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

……………………………………………….

……………………………………………….

……………………………………………….

……………………………………………….

……………………………………………….

……………………………………………….

……………………………………………….

---------------------------------------------------

Ran 2500 test in 0.002s

OK

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()

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 Web browser, omitting only JavaScript

support.”

Thanks to Terry!

And apologies to @voidspace…