testing should be very helpful I like the approach of urllib tests for JSON requests and responses easy enough to create and verify that way

requested [2011.01.28 08:52:15] just use a basic urllib2 script for testing since we're not always getting full results (nor are the forms obvious)

requested [2011.01.26 19:38:37] look up test notes (merged with communicate?)

requested [2011.01.26 19:35:28] write a super simple jquery script callable from the web with test functions for scorelogger app that way those won't need to change so often and functionality can be tested.

could also use any form of other testing: windmill, other simplified python scripts that way will know if the app server is behaving correctly or if the client is behaving correctly

for web based testing, check various scrape notes... it's a very similar process these are currently part of the communicate module (in the works)

/c/communicate/code/communicate/scrape/scrape-notes.txt twill and windmill are two favorites for this task

Unit testing is a good habit to get into. There are many unit testing frameworks for Python. Pylons uses one called nosetests and I have been very pleased with it. Here are a few notes I've collected on the topic:

in pylons project directory, should just be able to run nosetests

if tests are not being run, be sure that the test_* files do not have the executable permission flag set on the filesystem

nose will IGNORE those!

#2008.12.09 08:38:33 sudo chmod -R 664 pose/tests/functional/*

make sure not to chmod the directory itself to 664... that will prevent the system from being able to browse dir!

import pdb; pdb.set_trace()

in pylons import nose; nose.tools.set_trace() or nosetests --nocapture --with-pylons=test.ini from comments in: http://wiki.pylonshq.com/display/pylonsdocs/Unit+Testing or python setup.py nosetests