Easy way to create mock Request objects for testing views

[simon]

The testing framework currently encourages hooking up a view function using a URLconf and then using the TestClient to run tests against the view.

It would be nice if there was an easy way to bypass URLconf entirely in testing and just create a mock object representing a GET / POST / etc request, then pass that directly to the view function.

See this thread: ​http://groups.google.com/group/django-developers/browse_thread/thread/db86050095ebe5db

And this snippet: ​http://www.djangosnippets.org/snippets/963/

[Zellyn Hunter]

I'd suggest creating new methods (preferably on the existing Client class - it's just a refactoring of the initial code from the existing methods), so that it would be easy to intermix use of the normal get() and post() methods and the new variations while sharing the same session data.

[Zellyn Hunter]

After more experimentation it appears that a more complicated refactoring is necessary if this is to work with sessions, etc. The request middleware needs to run.

[Zellyn Hunter]

ps. it appears I accidentally messed with the needs_better_patch, needs_tests, and needs_docs settings - how do I tell what they were originally?

[(none)]

Milestone post-1.0 deleted

[Kevin Kubasik]

I have added support in django.test.mocks based on the snippet. Still needs docs and tests.

[Peter Bengtsson]

Replying to kkubasik:

I have added support in django.test.mocks based on the snippet. Still needs docs and tests.

Where? In a branch? I can't find anything in the trunk.

[Russell Keith-Magee]

Implemenation of RequestFactory as base class for Client

[Russell Keith-Magee]

(In [14191]) Fixed #9002 -- Added a RequestFactory. This allows you to create request instances so you can unit test views as standalone functions. Thanks to Simon Willison for the suggestion and snippet on which this patch was originally based.

[anonymous]

This needs some triage love