This document provides a humorous list of 10 reasons why a testing tool may not be used. It mocks various issues like the tool being for behavior driven development which is unpopular, having poor documentation, tests that don't work, running tests too fast to be useful, too many assert functions to choose from, only supporting unpopular versions of Python, being another mocking library, and claiming to support web testing but lacking JavaScript support. The document thanks Terry and apologies to voidspace.

1. The 2012 TiPBoF

2. Shout Outs!

3. Paul Hildebrandt & Disney
Heroku
Jesse Noller
Ewa Jodlowska
Peter Kropf

4. Thank YOU!

5. Let’s Start the Show

6. Top 10 Reasons No One Uses
Your Testing Tool.
The Python Testing Cabal

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. 9. Your test tool requires inheritance
and use CamelCase, so everyone
thinks it’s actually for Java code.
Cheap shot, I know.

9. 8. Your documentation sucks.
“See examples for information on use.”

10. 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!”

11. 6. Your own tests don’t work
Irony, thy name is open source.

12. 5. Your tool runs tests so fast, they
can’tactually be doing anything.
% bernhardtests
……………………………………………….
……………………………………………….
……………………………………………….
……………………………………………….
……………………………………………….
……………………………………………….
……………………………………………….
---------------------------------------------------
Ran 2500 test in 0.002s
OK

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. 3. Your testing tool is only for
Python3…
…which no one uses.

15. 2. It’s another fucking mock library.
‘nuff said.

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. Thanks to Terry!
And apologies to @voidspace…