testing Django against many Pythons and databases
Gary Wilson
snippet:
http://www.djangosnippets.org/snippets/106/
but I was wondering what other developers' thoughts would be on adding
something like this to Django proper. I'm just thinking that Django
should be able to test itself completely without any outside help.
This sort of thing would also be useful in case we ever wanted to do
some automated gate keeping of the checkins.
Gary
Malcolm Tredinnick
Probably not a good idea. It's not entirely trivial to get everything
set up to do this sort of all-in-one testing, so it has very limited
utility to the broader population. If you want to do it for automatic
post-commit checking, it's a buildbot or putting the stuff in the
post-commit script.
Usually you're going to be running against one version and one database
wrapper at a time anyway (if there's any chance of something failing),
because otherwise any failures will really stack up. If you think
everything is going to pass and want to run against the lot, it's a two
line shell script, more or less (loop over PATH, python binary names and
settings file names). I don't see it as solving the hard bit of any
problem -- getting a setup that can support all six current database
backends and three Python versions is 98% of the work required. Actually
running the tests is then trivial.
So -1 from me. Extra stuff to maintain (otherwise, I'd be -0) that isn't
going to add a lot of value to most setups or make anything much easier
than it already is.
Cheers,
Malcolm
--
Everything is _not_ based on faith... take my word for it.
http://www.pointy-stick.com/blog/