> > It's REALLY useful to have a small set of "functional tests" which can > be run in a live web app. For example, for an online purchase > process, you might have a selenium test which steps right through a > purchase using a known "only for tests" account or credit card number. > And it's an absolute lifesaver to have a bunch of CSS/JS URLs you hit > to verify a 200, so you don't go live with half your javascript > missing due to some static/media mixup in a settings file. > > Once you have something like this, you can quickly check that your > deployment (whether to UAT, staging or live) actually worked. > > I don't know what this kind of testing is called though ;-) >
Sounds like "smoke testing" to me. _______________________________________________ python-uk mailing list python-uk@python.org http://mail.python.org/mailman/listinfo/python-uk
