#10482 closed (fixed)
Unify access to response.context in test client
| Reported by: | Julien Phalip | Owned by: | Julien Phalip |
|---|---|---|---|
| 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: | no | UI/UX: | no |
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)
Change History (5)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
by , 16 years ago
| Attachment: | 10482.consistent_response_context.diff added |
|---|
Patch contains tests and doc.
comment:2 by , 16 years ago
| Component: | Uncategorized → Testing framework |
|---|---|
| milestone: | → 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 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
+1 to this change.