Test Client response does not contain Context with nested requests

[bmihelac]

get() and post() methods returns Response object, including context variable that was used to render the template that produced the response content.

However, if view calls another view before returning response, processing nested view will disconnect template_rendered signal returning no Context object.

I am attaching failing test case.

[bmihelac]

Failing test is in my github branch:

​https://github.com/bmihelac/django-1/tree/18356-test-client-context-lost-for-nested-views

[bmihelac]

Fix for this can be in giving dispatch_uid unique value for each request. This is added to branch and pull request if there are no objections.

[Aymeric Augustin]

Well, the test client wasn't designed to be used from within a view.

Could you show us the patch that would fix this problem?

[anonymous]

Changeset that fixes this issue is:

​https://github.com/bmihelac/django-1/commit/86a374e4d149b9a11aedc69753ce91b46669d16e

(branch has test case and fix)

BTW, i found this issue while trying to fix django-test-utils, which has middleware that records context for every request made. Testing that necessarily leads to nesting requests in a test case.

[bmihelac]

Accidentally posted this as anonymous.

[Aymeric Augustin]

This is quite an edge case, but I can't see any downside to the fix.

[Tim Graham <timograham@…>]

In 0cac4fbf699bb6a3de5f4a48c6e047a4dc6c2df7:

Fixed #18356 -- Gave the test client signals.template_rendered call a unique dispatch_uid

This prevents the test client context from being lost when the client
is used in a nested fashion.