#12089: test client fails to collect sub-contexts
---------------------------------------------+------------------------------
Reporter: akaihola | Owner: nobody
Status: new | Milestone:
Component: Testing framework | Version: SVN
Resolution: | Keywords: template context
TestClient
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by russellm):
IMHO, Backwards incompatibilities in test suites are even *more* important
than backwards incompatibilities in production code. If updating your
Django version can cause large portions of your test suite to fail, you
still have the problem of working out if the problem is failures in your
code, or in your tests.
(3) is probably my preferred option of the 4 you mention, but I'm still
not completely sold.
Thinking out loud - it strikes me that a 'sub context' should actually be
collected as a 'sub'. That is, if you inspect context[3], and it generated
2 subcontexts, you should be able to inspect context[3].context[0]. I
haven't even begun to look into the practicalities of this; I'm just
throwing out ideas that make sense to me from a public API point of view.
--
Ticket URL: <http://code.djangoproject.com/ticket/12089#comment:12>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
