Comment 3 for bug 819427

I like the feature but haven't reviewed the patch yet. Most of the following points are probably already covered in the patch:

* It will need doc updates
* The setup / teardown must be run in the same execution context as the test
* It must play well with the csv feature (should do by default)
* On instinct I dislike the mixed casing of setUp.py but using setup.py clashes with the established meaning of that filename
* The setup and teardown files must not be recognised as tests

Having a setup and teardown heirarchy, including allowing it in shared directory, would be *nice* - but isn't a requirement for an initial implementation.