- Each of the ``repoze.bfg.view.render_view``,

  ``repoze.bfg.view.render_view_to_iterable``,
  ``repoze.bfg.view.render_view_to_response``,
  ``repoze.bfg.view.append_slash_notfound_view``,
  ``repoze.bfg.view.default_notfound_view``,
  ``repoze.bfg.view.default_forbidden_view``, and the
  ``repoze.bfg.configuration.rendered_response`` functions now expects
  to be called with a request object that has a ``registry`` attribute
  which represents the current ZCA registry.  This should only be a
  problem when passing a custom request object to code which ends up
  calling these functions in a unit test.  To retrofit tests that end
  up calling these functions which expect to be able to use a
  non-registry-aware request object, use the
  ``repoze.bfg.threadlocal.get_current_request`` API in the test to
  create the request; this will return a
  ``repoze.bfg.testing.DummyRequest`` that has the current registry as
  its ``registry`` attribute.  Alternatively, use the
  ``repoze.bfg.threadlocal.get_current_registry`` API: call this
  function and add an attribute to your unit test request object named
  ``registry`` with the result.

- The ``repoze.bfg.view.derive_view`` callable has been removed.  Use
  ``repoze.bfg.configuration.Configurator.derive_view`` instead (still
  not an API, however).

1 files changed, 3 insertions, 1 deletions

diff --git a/repoze/bfg/testing.py b/repoze/bfg/testing.py
index 128e5cf32..79fa3bb9c 100644
--- a/repoze/bfg/testing.py
+++ b/repoze/bfg/testing.py
@@ -538,7 +538,9 @@ def setUp():
     from repoze.bfg.registry import Registry
     registry = Registry('testing')
     manager.clear()
-    manager.push({'registry':registry, 'request':None})
+    request = DummyRequest()
+    request.registry = registry
+    manager.push({'registry':registry, 'request':request})
     getSiteManager.sethook(get_current_registry)
     _clearContext()