Re: Django testing strategy

On Thu, Oct 4, 2012, Daniele Procida wrote: >I have started writing my first tests, for a project that has become >pretty large (several thousand lines of source code). >I'd appreciate any advice. Many thanks for the advice and suggestions. This is what I have produced so

Re: Django testing strategy

This has been a very interesting thread - out of interest, does anyone have a preference for one of factory-boy or django-dynamic-fixture and why? They look similarly up to date and useful, but I've no idea how to differentiate them. cheers L. -- ...we look at the present day through a

Re: Django testing strategy

There are a couple of problems with setting up a big database and then writing integration tests. Your tests will be slow, so they won't get run. They'll also be increasingly hard to maintain. Fixtures only seem make that worse. You've already got a code base that needs maintaining, you don't

Re: Django testing strategy

I've been using factory-boy as of late, and have found it to be a great way to setup each test exactly as I need it. Fixtures aren't bad either, but working with a large amount of data can make it difficult to predict the proper output for a test, and changes to this data to accommodate a new

Re: Django testing strategy

On Friday, October 5, 2012 9:56:34 AM UTC+2, Daniele Procida wrote: > > On Thu, Oct 4, 2012, Evan Brumley > wrote: > > >django-dynamic-fixture can also help a lot in this situation: > >http://paulocheque.github.com/django-dynamic-fixture/ > > > >Certainly beats having

Re: Django testing strategy

On Thursday, October 4, 2012 7:49:19 PM UTC+2, Daniele Procida wrote: > > I have started writing my first tests, for a project that has become > pretty large (several thousand lines of source code). > That is too, late! ;-) > > What needs the most testing - where most of the bugs or

Re: Django testing strategy

Please ignore this message I've hit «Post» by mistake I will edit my post :) -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/0S78LxSWkXoJ. To post to

Re: Django testing strategy

On Thursday, October 4, 2012 7:49:19 PM UTC+2, Daniele Procida wrote: > > I have started writing my first tests, for a project that has become > pretty large (several thousand lines of source code). > That is too, late! ;-) > > What needs the most testing - where most of the bugs or

Re: Django testing strategy

On Thu, Oct 4, 2012, Evan Brumley wrote: >django-dynamic-fixture can also help a lot in this situation: >http://paulocheque.github.com/django-dynamic-fixture/ > >Certainly beats having to futz around with fixtures. Thanks - there seem to be a lot of tools to generate

Re: Django testing strategy

django-dynamic-fixture can also help a lot in this situation: http://paulocheque.github.com/django-dynamic-fixture/ Certainly beats having to futz around with fixtures. On Friday, October 5, 2012 3:49:19 AM UTC+10, Daniele Procida wrote: > > I have started writing my first tests, for a project

Re: Django testing strategy

You can use `fixtures` for this purpose! You can have several of them to have exactly the data you need for a test. Have a look there: https://docs.djangoproject.com/en/dev/topics/testing/#django.test.TestCase.fixtures Cheers, Thomas 2012/10/4 Daniele Procida > I have

Django testing strategy

I have started writing my first tests, for a project that has become pretty large (several thousand lines of source code). What needs the most testing - where most of the bugs or incorrect appear emerge - are the very complex interactions between objects in the system. To me, the intuitive way