Re: Site testing How-To

2006-06-07 Thread Michael Radziej
Hi, Just a little teaser: I've found a nice approach to test your views. The problem is, the http response is hard to test, since you have to either scrape the interesting content from it, or use regexps. Both is not really nice. My approach does not check the actual http response, but the co

Re: Site testing How-To

2006-06-07 Thread Matthew Flanagan
On 6/7/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > > On Jun 7, 2006, at 3:54 AM, Simon Willison wrote: > > > > > > > On 7 Jun 2006, at 05:33, Joseph Kocherhans wrote: > > > >> I think you want tocreate something like testsettings.py, and in that > >> file do something like: > >> > >> from

Re: Site testing How-To

2006-06-07 Thread Todd O'Bryan
On Jun 7, 2006, at 3:54 AM, Simon Willison wrote: > > > On 7 Jun 2006, at 05:33, Joseph Kocherhans wrote: > >> I think you want tocreate something like testsettings.py, and in that >> file do something like: >> >> from myproject.settings import * >> >> then override the specific settings you

Re: Site testing How-To

2006-06-07 Thread Jeroen Ruigrok van der Werven
On 6/7/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > I think I'll use Selenium to test my site, but how should I change to > a test database, populate the test database, etc.? You might like twill as well: http://twill.idyll.org/ http://agiletesting.blogspot.com/2005/09/web-app-testing-with-pyth

Re: Site testing How-To

2006-06-07 Thread Simon Willison
On 7 Jun 2006, at 05:33, Joseph Kocherhans wrote: > I think you want tocreate something like testsettings.py, and in that > file do something like: > > from myproject.settings import * > > then override the specific settings you want. It won't work with > manage.py, but your tests should be

Re: Site testing How-To

2006-06-07 Thread Simon Willison
On 7 Jun 2006, at 02:42, Todd O'Bryan wrote: > Does anybody have a best practice (or not-too-annoying practice) for > testing? > > I think I'll use Selenium to test my site, but how should I change to > a test database, populate the test database, etc.? This is an area where Django can learn a

Re: Site testing How-To

2006-06-07 Thread Brett Parker
On Tue, Jun 06, 2006 at 10:33:42PM -0600, Joseph Kocherhans wrote: > > On 6/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > > > Does anyone know of a way to get all attributes of a module into > > another module while overriding just a few? > > I think you want tocreate something like testsett

Re: Site testing How-To

2006-06-06 Thread Joseph Kocherhans
On 6/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > Does anyone know of a way to get all attributes of a module into > another module while overriding just a few? I think you want tocreate something like testsettings.py, and in that file do something like: from myproject.settings import *

Re: Site testing How-To

2006-06-06 Thread Todd O'Bryan
On Jun 6, 2006, at 11:10 PM, Don Arbow wrote: > For unit testing, you don't really need a database. You can always > mock the database calls, because you're not testing the data or the > database (if postgres is up, the database is working), you're > testing your code's behavior to the data

Re: Site testing How-To

2006-06-06 Thread Don Arbow
On Jun 6, 2006, at 6:42 PM, Todd O'Bryan wrote:Does anybody have a best practice (or not-too-annoying practice) for  testing?I think I'll use Selenium to test my site, but how should I change to  a test database, populate the test database, etc.?If you want to test your model relationships, I find