Code

Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#10482 closed (fixed)

Unify access to response.context in test client

Reported by: julien Owned by: julien
Component: Testing framework Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

James Bennett described the issue quite clearly on this django-developers thread: http://groups.google.com/group/django-developers/browse_thread/thread/1b10084ea969141e

To simplify the testing of templates and contexts, it'd be good to have a unified way to access the response.context attribute.

Attachments (1)

10482.consistent_response_context.diff (5.8 KB) - added by julien 5 years ago.
Patch contains tests and doc.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by ericholscher

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

+1 to this change.

Changed 5 years ago by julien

Patch contains tests and doc.

comment:2 Changed 5 years ago by julien

  • Component changed from Uncategorized to Testing framework
  • milestone set to 1.1

The patch is backward compatible. I hope it makes it into 1.1 as it makes testers' life a bit easier. And we want testers' life to be easy ;)

comment:3 Changed 5 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [10084]) Fixed #10482 -- Unified access to response.context when inspecting responses from the test client. Thanks to James Bennett for the design, and Julien Phalip for the patch.

comment:4 Changed 3 years ago by jacob

  • milestone 1.1 deleted

Milestone 1.1 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.