Logo     Photos

16 Member(s) Online

PyCon is a 100%
Volunteer-run
Conference Organized by
Members of the
Python
Community.

Site/Questions etc ?

Valid XHTML 1.0 Transitional

Valid CSS!

 
PyCon 2007 is sponsored
in part by
Zenoss - The Next Step in IT Management Google Microsoft .Net Framework EWT LLC Enthought, Inc.
Platinum
Wingware Python IDE Accense Technology, Inc.
Gold
Quality Vision International Inc. MerchantCircle Big Nerd Ranch, Inc. Canonical
Silver

Details of Talk

#087: 005 twill, scotch, and figleaf -- tools for testing
Author(s):
Dr. C. Titus Brown
Items: audio-no    handouts-no    released-unknown    video-no    ADMIN
Abstract:

twill, scotch, and figleaf are recent additions to the suite of Python-based testing tools. twill is a simple Web-scripting framework based on mechanize that lets users automate Web browsing with a simple language; scotch is a WSGI proxy server & Web traffic recorder that lets users record and replay raw WSGI/HTTP traffic and translate it into twill script; and figleaf is a code coverage recorder and analyzer that is aimed at integration with large projects where coverage.py may be less suitable. I'll briefly discuss the genesis of the tools and their architecture, and I'll spend most of the time demonstrating how to combine these tools with others in order to build automated tests for Python projects.

Outline:

  1. introduction to using twill for functional web testing 2. introduction to using scotch/WSGI for web recording and playback 3. introduction to using figleaf for code coverage analysis 4. automating functional web testing in a unit test framework 5. using code coverage with unit testing to target new tests 6. instrumenting remote web sites for code coverage 7. integrating web testing with development, a demonstration 8. demonstration: automated testing of a django demo site 9. demonstration: automated testing of a cherrypy demo site 10. demonstration: automated testing of trac
Item(s):

Release Form not on File

Note: Talk recordings have come from different donors, with different levels of quality. A suffix has been added to the basename of each recording reflecting this. For eventual upload to a repository like archive.org, a formal naming convention has been followed:

pycon-{date}-{track}-{timeslot}-{talkno}-{donor}.mp3

For those who might prefer a more human-meaningful name, the recordings have MP3/Ogg/Flac ID3 information within and a simple python script could rename your collection to something in a {title}-{author} form.