[TIP] Web Application Testing Code of Ethics?
noah.gift at gmail.com
Fri Nov 21 18:27:16 PST 2008
On Fri, Nov 21, 2008 at 6:21 AM, Nicolas Chauvat <nicolas.chauvat at logilab.fr
> On Fri, Nov 21, 2008 at 09:40:54AM +1100, Ben Finney wrote:
> > I recommend "Your code isn't done until I have a complete automated
> > test suite from you that I can run to see all requirements
> > demonstrated working."
> At Logilab, we try to go as far as "your code isn't done until I have
> a debian package that installs cleanly on the staging server that's
> mirrored from the production server". Then we run the database migration
> script on the staging server and run the test suite. Usually it takes
> a couple tries to get right and install on the production server with
> Deployment is actual work. Mistaking deployment with file-copying has
> a cost called down-time. The only solution I know is to test the deployment
I agree, scp is a poor choice for deployment, and not testing is a poor
choice for deployment. It seems like I haven't read much of anything about
this aspect of testing, although Grig might touched on some of these topics
with his configuration management blog post.
This might be the time to figure out how this process could be integrated
into something like buildout, paver, or virtualenv bootstrap, and with
testing framework. Of course it would be awesome if that framework tested
not just python code but most language code. That would be an interesting
growth area for python, being the king of testing no matter what the
> Nicolas Chauvat
> logilab.fr - services en informatique scientifique et gestion de
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python