|author:||Ian Bicking <email@example.com>|
|maintainer:||Gael Pasgrimaud <firstname.lastname@example.org>|
WebTest is an extraction of paste.fixture.TestApp, rewriting portions to use WebOb. It is under active development as part of the Pylons cloud of packages.
This library is licensed under an MIT-style license.
You can use pip or easy_install to get the latest stable release:
$ pip install WebTest $ easy_install WebTest
Or if you want the development version:
$ pip install https://nodeload.github.com/Pylons/webtest/tar.gz/master
WebTest helps you test your WSGI-based web applications. This can be any application that has a WSGI interface, including an application written in a framework that supports WSGI (which includes most actively developed Python web frameworks – almost anything that even nominally supports WSGI should be testable).
With this you can test your web applications without starting an HTTP server, and without poking into the web framework shortcutting pieces of your application that need to be tested. The tests WebTest runs are entirely equivalent to how a WSGI HTTP server would call an application. By testing the full stack of your application, the WebTest testing model is sometimes called a functional test, integration test, or acceptance test (though the latter two are not particularly good descriptions). This is in contrast to a unit test which tests a particular piece of functionality in your application. While complex programming tasks are often suited to unit tests, template logic and simple web programming is often best done with functional tests; and regardless of the presence of unit tests, no testing strategy is complete without high-level tests to ensure the entire programming system works together.
WebTest helps you create tests by providing a convenient interface to run WSGI applications and verify the output.
The most important object in WebTest is TestApp, the wrapper for WSGI applications. It also allows you to perform HTTP requests on it. To use it, you simply instantiate it with your WSGI application.
If your WSGI application requires any configuration, you must set that up manually in your tests.
Here is a basic application:
>>> def application(environ, start_response): ... headers = [('Content-Type', 'text/html; charset=utf8'), ... ('Content-Length', str(len(body)))] ... start_response('200 Ok', headers) ... return [body]
Wrap it into a TestApp:
>>> from webtest import TestApp >>> app = TestApp(application)
Then you can get the response of a HTTP GET:
>>> resp = app.get('/')
And check the results, like response’s status:
>>> assert resp.status == '200 Ok' >>> assert resp.status_int == 200
>>> assert resp.content_type == 'text/html' >>> assert resp.content_length > 0
Or response’s body:
>>> resp.mustcontain('<html>') >>> assert 'form' in resp
WebTest can do much more. In particular, it can handle Form handling and json.
Copyright (c) 2010 Ian Bicking and Contributors
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.