tornado.testing
— Unit testing support for asynchronous code¶
Support classes for automated testing.
AsyncTestCase
andAsyncHTTPTestCase
: Subclasses of unittest.TestCase with additional support for testing asynchronous (IOLoop
based) code.ExpectLog
andLogTrapTestCase
: Make test logs less spammy.main()
: A simple test runner (wrapper around unittest.main()) with support for the tornado.autoreload module to rerun the tests when code changes.
Asynchronous test cases¶
-
class
tornado.testing.
AsyncTestCase
(methodName='runTest', **kwargs)[source]¶ TestCase
subclass for testingIOLoop
-based asynchronous code.The unittest framework is synchronous, so the test must be complete by the time the test method returns. This means that asynchronous code cannot be used in quite the same way as usual. To write test functions that use the same
yield
-based patterns used with thetornado.gen
module, decorate your test methods withtornado.testing.gen_test
instead oftornado.gen.coroutine
. This class also provides thestop()
andwait()
methods for a more manual style of testing. The test method itself must callself.wait()
, and asynchronous callbacks should callself.stop()
to signal completion.By default, a new
IOLoop
is constructed for each test and is available asself.io_loop
. ThisIOLoop
should be used in the construction of HTTP clients/servers, etc. If the code being tested requires a globalIOLoop
, subclasses should overrideget_new_ioloop
to return it.The
IOLoop
‘sstart
andstop
methods should not be called directly. Instead, useself.stop
andself.wait
. Arguments passed toself.stop
are returned fromself.wait
. It is possible to have multiplewait
/stop
cycles in the same test.Example:
# This test uses coroutine style. class MyTestCase(AsyncTestCase): @tornado.testing.gen_test def test_http_fetch(self): client = AsyncHTTPClient(self.io_loop) response = yield client.fetch("http://www.tornadoweb.org") # Test contents of response self.assertIn("FriendFeed", response.body) # This test uses argument passing between self.stop and self.wait. class MyTestCase2(AsyncTestCase): def test_http_fetch(self): client = AsyncHTTPClient(self.io_loop) client.fetch("http://www.tornadoweb.org/", self.stop) response = self.wait() # Test contents of response self.assertIn("FriendFeed", response.body) # This test uses an explicit callback-based style. class MyTestCase3(AsyncTestCase): def test_http_fetch(self): client = AsyncHTTPClient(self.io_loop) client.fetch("http://www.tornadoweb.org/", self.handle_fetch) self.wait() def handle_fetch(self, response): # Test contents of response (failures and exceptions here # will cause self.wait() to throw an exception and end the # test). # Exceptions thrown here are magically propagated to # self.wait() in test_http_fetch() via stack_context. self.assertIn("FriendFeed", response.body) self.stop()
-
get_new_ioloop
()[source]¶ Creates a new
IOLoop
for this test. May be overridden in subclasses for tests that require a specificIOLoop
(usually the singletonIOLoop.instance()
).
-
stop
(_arg=None, **kwargs)[source]¶ Stops the
IOLoop
, causing one pending (or future) call towait()
to return.Keyword arguments or a single positional argument passed to
stop()
are saved and will be returned bywait()
.
-
wait
(condition=None, timeout=None)[source]¶ Runs the
IOLoop
until stop is called or timeout has passed.In the event of a timeout, an exception will be thrown. The default timeout is 5 seconds; it may be overridden with a
timeout
keyword argument or globally with theASYNC_TEST_TIMEOUT
environment variable.If
condition
is not None, theIOLoop
will be restarted afterstop()
untilcondition()
returns true.Changed in version 3.1: Added the
ASYNC_TEST_TIMEOUT
environment variable.
-
-
class
tornado.testing.
AsyncHTTPTestCase
(methodName='runTest', **kwargs)[source]¶ A test case that starts up an HTTP server.
Subclasses must override
get_app()
, which returns thetornado.web.Application
(or otherHTTPServer
callback) to be tested. Tests will typically use the providedself.http_client
to fetch URLs from this server.Example, assuming the “Hello, world” example from the user guide is in
hello.py
:import hello class TestHelloApp(AsyncHTTPTestCase): def get_app(self): return hello.make_app() def test_homepage(self): response = self.fetch('/') self.assertEqual(response.code, 200) self.assertEqual(response.body, 'Hello, world')
That call to
self.fetch()
is equivalent toself.http_client.fetch(self.get_url('/'), self.stop) response = self.wait()
which illustrates how AsyncTestCase can turn an asynchronous operation, like
http_client.fetch()
, into a synchronous operation. If you need to do other asynchronous operations in tests, you’ll probably need to usestop()
andwait()
yourself.-
get_app
()[source]¶ Should be overridden by subclasses to return a
tornado.web.Application
or otherHTTPServer
callback.
-
fetch
(path, **kwargs)[source]¶ Convenience method to synchronously fetch a url.
The given path will be appended to the local server’s host and port. Any additional kwargs will be passed directly to
AsyncHTTPClient.fetch
(and so could be used to passmethod="POST"
,body="..."
, etc).
-
-
class
tornado.testing.
AsyncHTTPSTestCase
(methodName='runTest', **kwargs)[source]¶ A test case that starts an HTTPS server.
Interface is generally the same as
AsyncHTTPTestCase
.
-
tornado.testing.
gen_test
(func=None, timeout=None)[source]¶ Testing equivalent of
@gen.coroutine
, to be applied to test methods.@gen.coroutine
cannot be used on tests because theIOLoop
is not already running.@gen_test
should be applied to test methods on subclasses ofAsyncTestCase
.Example:
class MyTest(AsyncHTTPTestCase): @gen_test def test_something(self): response = yield gen.Task(self.fetch('/'))
By default,
@gen_test
times out after 5 seconds. The timeout may be overridden globally with theASYNC_TEST_TIMEOUT
environment variable, or for each test with thetimeout
keyword argument:class MyTest(AsyncHTTPTestCase): @gen_test(timeout=10) def test_something_slow(self): response = yield gen.Task(self.fetch('/'))
New in version 3.1: The
timeout
argument andASYNC_TEST_TIMEOUT
environment variable.Changed in version 4.0: The wrapper now passes along
*args, **kwargs
so it can be used on functions with arguments.
Controlling log output¶
-
class
tornado.testing.
ExpectLog
(logger, regex, required=True)[source]¶ Context manager to capture and suppress expected log output.
Useful to make tests of error conditions less noisy, while still leaving unexpected log entries visible. Not thread safe.
The attribute
logged_stack
is set to true if any exception stack trace was logged.Usage:
with ExpectLog('tornado.application', "Uncaught exception"): error_response = self.fetch("/some_page")
Changed in version 4.3: Added the
logged_stack
attribute.Constructs an ExpectLog context manager.
Parameters: - logger – Logger object (or name of logger) to watch. Pass an empty string to watch the root logger.
- regex – Regular expression to match. Any log entries on the specified logger that match this regex will be suppressed.
- required – If true, an exeption will be raised if the end of
the
with
statement is reached without matching any log entries.
-
class
tornado.testing.
LogTrapTestCase
(methodName='runTest')[source]¶ A test case that captures and discards all logging output if the test passes.
Some libraries can produce a lot of logging output even when the test succeeds, so this class can be useful to minimize the noise. Simply use it as a base class for your test case. It is safe to combine with AsyncTestCase via multiple inheritance (
class MyTestCase(AsyncHTTPTestCase, LogTrapTestCase):
)This class assumes that only one log handler is configured and that it is a
StreamHandler
. This is true for bothlogging.basicConfig
and the “pretty logging” configured bytornado.options
. It is not compatible with other log buffering mechanisms, such as those provided by some test runners.Deprecated since version 4.1: Use the unittest module’s
--buffer
option instead, orExpectLog
.Create an instance of the class that will use the named test method when executed. Raises a ValueError if the instance does not have a method with the specified name.
Test runner¶
-
tornado.testing.
main
(**kwargs)[source]¶ A simple test runner.
This test runner is essentially equivalent to
unittest.main
from the standard library, but adds support for tornado-style option parsing and log formatting.The easiest way to run a test is via the command line:
python -m tornado.testing tornado.test.stack_context_test
See the standard library unittest module for ways in which tests can be specified.
Projects with many tests may wish to define a test script like
tornado/test/runtests.py
. This script should define a methodall()
which returns a test suite and then calltornado.testing.main()
. Note that even when a test script is used, theall()
test suite may be overridden by naming a single test on the command line:# Runs all tests python -m tornado.test.runtests # Runs one test python -m tornado.test.runtests tornado.test.stack_context_test
Additional keyword arguments passed through to
unittest.main()
. For example, usetornado.testing.main(verbosity=2)
to show many test details as they are run. See http://docs.python.org/library/unittest.html#unittest.main for full argument list.
Helper functions¶
-
tornado.testing.
bind_unused_port
(reuse_port=False)[source]¶ Binds a server socket to an available port on localhost.
Returns a tuple (socket, port).
-
tornado.testing.
get_unused_port
()[source]¶ Returns a (hopefully) unused port number.
This function does not guarantee that the port it returns is available, only that a series of get_unused_port calls in a single process return distinct ports.
Deprecated since version Use: bind_unused_port instead, which is guaranteed to find an unused port.