On Tuesday 02 September 2014 15:27:53 Josh Smeaton wrote:
>
> As far as I'm concerned, using fixtures is the wrong way to populate data
> for tests. You're much better off creating the objects you need for each
> test within the test, or creating them directly inside the setUp method.
+1.
> You
Hey Josh,
Thanks for the answer, I'll give the factory boy a shot. I just don't like
to put code that populate fields in the setup function (especially when
using nested relations). It's just a lot of code to achieve it and lost
time to me. (I normally use the current test database and dump rele
The idea isn't bad, except that the performance of fixture loading is
pretty terrible in general. Take a look at
ticket https://code.djangoproject.com/ticket/20392 for some performance
profiling and discussion.
As far as I'm concerned, using fixtures is the wrong way to populate data
for tests
Hello,
I thought it might be pretty helpful if there was a load_fixtures annotation
that loads fixture for a specific test method in TransactionTestCase. On some
occasions, it might be pretty hard to test a model/view that uses only one or a
few fixtures that are always the same. Here are some o
