#28983: Documentation on providing initial data with migrations is unhelpful
-------------------------------------+-------------------------------------
     Reporter:  Rob Atkinson         |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  2.0
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Rob Atkinson):

 OK - testing style and deeper integration testing with services is out of
 scope - but i can't see why inheritance of tests isn't a key part of
 inheritance as a supported mechanism.

 There is also a detailed example of using fixtures, yet apparently using
 fixtures is deprecated  "Support for automatic loading of initial_data
 fixtures and initial SQL data will be removed."  all feels a little
 perverse and unhelpful trying to collate all these disparate pieces of
 information.

 To be consistent, what is needed is  an example of how to do a test
 rather than a simple ref to the low level docs.  This should come first,
 with a reference to the fixtures deprecation issue, and push the example
 of initial loading of fixtures to a separate page, or even better remove
 it and reference back to docs for previous versions.

 The FileField issue should be explicitly called out with a ref to #23251
 and a guideline provided  (should custom code for file CRUD handling be
 unit tested and if so an example of how?)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28983#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.2f40ddc168cdd8cdfecccd0d5a60d948%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to