Add an eventSessions at DjangoCon US 2011 about Testing
Your current filters are…
- Topic: Testing
Monday 5th September 2011
-
Test Anything, Test Everything
by Dave Dash
Testing in Django is easy if you're testing models against your database. What happens when you need to test other-systems, like a search engine, or an API? This tutorial will cover how I built SphinxTestCase, ESTestCase and redisutils to allow us to maintain test coverage on our web sites.
Testing backends other than your database can be tricky. It's entirely necessary, however, otherwise you'll start getting glaring holes in terms of coverage.
This tutorial will show you how to subclass TestCase and properly setup and teardown external systems.
It will also show you how to be nice to your other developers who may want to opt-out of testing backend systems (like search).
Tuesday 6th September 2011
-
Testing with Lettuce and Splinter
by Adam Nelson
Lettuce, adapted from Ruby's Cucumber, is a behavior driven development (BDD) testing suite that sits on top of Splinter - a web driver for simulating real-world usage of your site. Learn the ins and outs of BDD using Lettuce and Splinter for rapid deployment.
Yipit uses Lettuce and Splinter to simulate users moving through the actual site under different scenarios. Unlike unit testing, this allows a tester to find problems at various levels (including Javascript and HTML defects) and under various situations specific to a browser environment. This talk will introduce various tools available right now as well as how to write extensible tests for a production environment. Ways to integrate testing into the release process will also be discussed.
-
Testing: The Developer Strikes Back
by Sandy Strong
“Code not tested is broken by design” - Jacob Kaplan-Moss Every programming project has unique testing needs. It’s not always easy to understand what those needs are, or how to write tests that satisfy them. One of our goals as developers is to write tests that minimize failures in production that can cost our companies time, money, resources, and in many cases, hours of sleep!
Every programming project has unique testing needs. It’s not always easy to understand what those needs are, or how to write tests that satisfy them. One of our goals as developers is to write tests that minimize failures in production that can cost our companies time, money, resources, and in many cases, hours of sleep!