Currently we don't have any unit tests for checking that the framework is sane.
 I think we badly need to have these, and we should run them whenever we're
about to commit to CVS, and not commit until the tests pass.

Proposal:  
Create a simple app using pygtk and libglade, which exists purely for the sake
of running unit tests on the dogtail and pyspi API.  It would live in a
subdirectory of the toplevel dogtail directory.  We'd use the standard Python
"unittest" module, in the setup/teardown we'd run the app, we can then have
tests which drive the various methods in the API, checking that searches
succeed, that they fail where they should fail etc etc.

Possible names for the dummy app:
- treestump
- hydrant (too US-specific?)
- lamppost (too UK-specific?)
- tree (No: already taken)

Should the dummy app live in the dogtail module?  
Pros: ensures the visibility of it, makes it easy to run the unit tests
Cons: it could also be useful for writing unit tests for pyspi

Even without pyspi unit tests, if making changes to _pyspi_ I think we should
run the _dogtail_ unit tests and see if anything breaks there (this isn't
strictly doing unit tests for pyspi, but should catch any major breakages);
perhaps we should have proper pyspi unit tests as well.

Thoughts?