Re: [Django] #13439: repeated "No fixtures found." on manage.py test

[Django]

#13439: repeated "No fixtures found." on manage.py test
+---
  Reporter:  wkornewald | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  new => closed
  * resolution:  => worksforme

Comment:

 I haven't ever seen this. You'll need to provide a test case to
 demonstrate how and when this happens.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13439: repeated "No fixtures found." on manage.py test

[Django]

#13439: repeated "No fixtures found." on manage.py test
+---
  Reporter:  wkornewald | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabrielhurley):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I've had no luck duplicating this so far... I've tried having no fixtures,
 empty fixtures, etc. and I've tried it with a single TestCase class,
 multiple TestCase classes, multiple test methods on those classes,
 different verbosity levels... Every way I try it I only get the "no
 fixtures found." method once.

 I may be missing something. But for the sake of asking, are you doing
 something in the setUp or tearDown method that might be triggering this?

 Other thought: could this be a DB-specific problem where a fixture is
 being re-loaded each time instead of a rollback? My attempts at
 duplicating this bug are simply on sqlite.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.