Zope.app.wsgi

==================

- Fixed test breakage due to changes in mechanize 0.2.0.

==================

- Add support for testing XMLRPC using zope.app.wsgi.testlayer.

- Fix a bug in the status string handling in zope.app.wsgi.testlayer's
FakeResponse.

==================

- Return a FakeResponse object in zope.app.wsgi.testlayer.http,
so it becomes easier to port over tests from zope.app.testing's
HTTPCaller.

- X-Powered-By header is now stripped by zope.app.wsgi.testlayer as
it is by zope.app.testing.

- Bugfix: initialize any <logger> defined in the config, as
zope.app.server does. (Fixes 291147)

==================

- zope.app.wsgi.testlayer is now a lot more compatible with
the HTTPCaller() functionality in zope.app.testing, which it can
replace:

- same transaction behavior - pending transactions are committed
before request and synchronized afterwards.

- support for browser.handleErrors (for zope.testbrowser).

- support for clear-text (non-base64) Basic authentication headers,
which are easier to read in the tests (though not correct in
actual HTTP traffic).

==================

- Rewrite tests in order not to dependent on ``zope.app.testing`` and
``zope.app.zcmlfiles``.

- ``zope.app.wsgi.testlayer`` introduces new testing functionality that
can replace the old functionality in ``zope.app.testing``. In addition,
it supports using ``zope.testbrowser`` with WSGI directly (instead of
relying on ``zope.app.testing``, which pulls in a lot of dependencies).

The interesting parts are:

* ``zope.app.wsgi.testlayer.BrowserLayer``: this sets up a minimal layer
that allows you to use the new WSGI-enabled Browser.

* ``zope.app.wsgi.testlayer.Browser``: this is a subclass of Browser from
``zope.testbrowser.browser``. Use it instead of
``zope.testbrowser.browser`` directly to use the test browser with WSGI.
You need to use ``BrowserLayer`` with your tests for this to work.

* ``zope.app.wsgi.testlayer.http``: this is the equivalent to the ``http()``
function in ``zope.app.testing``. It allows low-level HTTP access
through WSGI. You need to use ``BrowserLayer`` with your tests for
this to work.

==================

- Support product configuration sections in Zope configuration files.