On 7/17/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > On 7/13/06, Simon Willison <[EMAIL PROTECTED]> wrote: > > > > The best way of running tests against a Django application, to my > > mind, is to run a "fake" web server (i.e. one that doesn't actually > > bind to a port) around the application. > > > Agreed; although I'm not sure that you actually need to run a server in the > 'start a process/thread' sense. A TestHandler() that operates much like the > mod_python or wsgi Handler objects (or a light wrapper around one of those > handlers that provides a nice testing interface) should be sufficient. > > > There's just one problem with this approach: while running assertions > > against an HttpResponse object is adequate, the ideal situation would > > be to run assertions against the template context as well. If you > > just run assertions against the HttpResponse object you end up having > > to process the HTML in some way to work out if the test has passed. > > >
I've been using on some none-django projects Twill testing framework (http://twill.idyll.org/). It's been a bit buggy though, but on the other hand all the bugs we've fixed at our company have been sent to the developer. Anyway, Twill's been an ideal tool for web testing, because you can give follow links, fill forms etc. -- Jyrki // [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
