Skip to main content

PyCon: Testing Tools in Python

I went to a two hour tutorial on testing. It was everything I hoped for. It was given by Grig Gheorghiu and Dr. C. Titus Brown. Here's an outline:
  • Unit tests:
    • Make sure your code works in isolation.
    • It's not a full code path.
    • He's purposely ignoring unit tests.
    • He encourages the confusion between unit tests and functional tests.
  • Functional tests:
    • Make sure your code works properly.
    • Use mock or live resources.
  • GUI tests:
    • Use a tool to record your interactions with an app and then play it back.
    • These are fragile.
  • Regression tests:
    • Making sure things don't get worse.
  • Acceptance tests:
    • "Unit tests ensure that you write the code right.
    • Acceptances tests ensure that you write the right code."
  • Mock testing:
    • Use "fake" resources so as to test your code with fewer dependencies.
    • Use mocking at the I/O boundaries.
  • nose:
    • You don't need to use the unittest API.
    • It's trivial. Write a test_foo.py module with a test_foo function. Run nose.
    • Unifies all the different test APIs.
    • Supports test fixtures via setup and teardown functions.
    • To test multiple apps: nosetests -w package0 -w package1 ...
    • If you have a lot of code, he recommends using nose from a Python script, not from the CLI.
    • The plugins are great.
  • Selenium:
    • This is GUI testing.
    • Test your AJAX.
    • Limited to a single Web site.
    • Really slick way to run tests in your browser.
    • You can script tests in Python.
    • Writing the scripts can be tedious, and they are fragile.
    • Useable for cross browser testing: Firefox, IE, Safari, Opera, etc.
    • Avoid it unless you're using AJAX.
  • My question: my tests pass, but I get bugs for cases I didn't consider:
    • You'll never:
      • Have complete code coverage.
      • Have tests for every situation.
      • Get away from the need for exploratory testing.
    • Automated tests free you up to do more exploratory testing.
    • When you find a bug, write test cases to try to flush out nearby bugs.
  • twill:
    • Speaker wrote it, and he likes it.
    • It's just a simple layer on top of other libraries.
    • Code in Python or "twill script".
    • In a sense, it is a scriptable browser, but it doesn't support JavaScript.
    • Run twill from within nose.
    • Can talk to WSGI directly.
    • It's lower level than Paste Fixture:
      • Unlike Paste Fixture, trivially toggle between direct WSGI or a live server.
  • figleaf:
    • A code coverage tool that's not restricted to just the CLI.
    • Code coverage is necessary, but not sufficient.
  • Continuous integration:
    • Continuous integration and buildbot are tremendously useful.
    • Distribute your building and testing across multiple platforms.
    • Tinderbox guys switched to buildbot.
    • For C and C++, he gave a plug for cmake.
    • You need to test in a cleanroom environment, on multiple platforms, in a developer neutral way.
    • Use a Subversion post commit hook to launch it.
  • Most important recommendations:
    • Start with some unit tests, some functional tests, and buildbot.
    • Build test fixtures as you need them, instead of ahead of time.
    • He's not a fan of test driven development.
      • This blew me away since he's foremost in the Python testing community.

Comments

Grig Gheorghiu said…
Shannon -- glad you found the tutorial useful! We'll put the slides online at some point, and add links to the tools we mentioned in the presentation.

Grig
jjinux said…
Thanks, Grig.

Happy Hacking!
Unknown said…
Hi Shannon,

I just wanted to say thanks for the great notes! :-) They helped me "get" the different types of tests a bit better.

I also decided to blog about your notes here.

Anyway, thanks again,
Krys
Unknown said…
Hi Shannon,

Your notes are enlightening. I've been using Selenium mostly because there are Firefox extensions that really help, like Selenium IDE. The IDE also allows you to test an app that hits multiple sites. I need this ability for what I'm doing.

Cheers,

Steve

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;)

In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3, Erlang, and the original Lisp machine. The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts.

Now, I'm sure that many of these ideas have already been envisioned within Tunes.org, LLVM, Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway.

Rather than wax philosophical, let me just dump out some ideas:Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code." I bet it&…