1) I've been using Factory Boy to create test data rather than fixtures.
It is so much easier to ensure that I know exactly what data is available
for a given test.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this
On Mon, Jul 8, 2013 at 5:41 PM, Larry Martell wrote:
> So if you don't use dump files, what do you do? Load data row by row
> from within your test's setups?
no, i mostly write the fixture data by hand. except when i need a
series of records to cover a all (most?)
On Mon, Jul 8, 2013 at 4:21 PM, Javier Guerra Giraldez
wrote:
> On Mon, Jul 8, 2013 at 4:14 PM, Larry Martell wrote:
>> It appesars it's trying to add a row to django_content_type and it's
>> already there. I tried not loading the fixture for
On Mon, Jul 8, 2013 at 4:14 PM, Larry Martell wrote:
> It appesars it's trying to add a row to django_content_type and it's
> already there. I tried not loading the fixture for django_content_type
> but I got the same error. These fixture files contain data I dumped
>
On Mon, Jul 8, 2013 at 12:06 PM, Larry Martell wrote:
> Still working on getting my tests to run. I have 2 issues right now:
>
> 1) I want to load data from fixture files. In this case I am trying to
> load auth data to test the logins. I have this in my test code:
>
>
Still working on getting my tests to run. I have 2 issues right now:
1) I want to load data from fixture files. In this case I am trying to
load auth data to test the logins. I have this in my test code:
from django.test import TestCase
from django.contrib.auth.models import User, Permission
6 matches
Mail list logo