#24622: Response "context" and "templates" not available in the Test Client when
using Jinja2 - Django 1.8
-------------------------------------+------------------------------------
Reporter: rivantis | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.8
Severity: Normal | Resolution:
Keywords: jinja2, test client | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by MoritzS):
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* needs_docs: 1 => 0
Comment:
I just spoke to Markus about that and he says the way
`assertTemplateUsed()` works should be consistent across template
backends. That means that if it checks for base templates and included
ones in the Django template engine (as it currently does) it should also
work for the other backends like Jinja2.
To make this consistent across the two current backends and potential new
ones Markus proposed adding a method called something like
`setup_test_environment()` to each template backend class that
(monkey-)patches the backend to send the `template_rendered` signal.
--
Ticket URL: <https://code.djangoproject.com/ticket/24622#comment:24>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f0cf447be1219066d6f0b92be1ee4b3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.