#11595: Fixture validation errors should report their data
-------------------------------------+-------------------------------------
Reporter: freyley | Owner: raulcd
Type: | Status: assigned
Cleanup/optimization | Component: Core (Serialization)
Milestone: | Severity: Normal
Version: 1.0 | Keywords: easy-pickings
Resolution: | Has patch: 1
Triage Stage: Accepted | Needs tests: 1
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Comment (by raulcd):
@russellm -- I am sorry I misunderstood the documentation. I thought the
meaning of the ready for chekin was set the ticket as "ey guys, can anyone
take a look, I did my patch". I will know that for the next one. About the
tests I executed the full test suite and as no test failed I thought the
"literal" of the error may not be tested. I will prepare the tests and
submit the new patch, just a question (as I am new) where do you think is
the best location to create the tests? In
/trunk/tests/modeltests/validation or create a new folder with the tests.
I am sorry for this questions, but as a newbie I want to follow your
standards.
--
Ticket URL: <http://code.djangoproject.com/ticket/11595#comment:11>
Django <http://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 post to this group, send email to django-updates@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.
