summaryrefslogtreecommitdiff
path: root/docs/quick_tutorial/functional_testing.rst
blob: c3d3299bcb590d0cf4de59f1a2e935622a7e3236 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
===================================
06: Functional Testing with WebTest
===================================

Write end-to-end full-stack testing using ``webtest``.

Background
==========

Unit tests are a common and popular approach to test-driven development
(TDD.) In web applications, though, the templating and entire apparatus
of a web site are important parts of the delivered quality. We'd like a
way to test these.

WebTest is a Python package that does functional testing. With WebTest
you can write tests which simulate a full HTTP request against a WSGI
application, then test the information in the response. For speed
purposes, WebTest skips the setup/teardown of an actual HTTP server,
providing tests that run fast enough to be part of TDD.

Objectives
==========

- Write a test which checks the contents of the returned HTML

Steps
=====

#. First we copy the results of the previous step, as well as install
   the ``webtest`` package:

   .. code-block:: bash

    (env)$ cd ..; cp -r unit_testing functional_testing; cd functional_testing
    (env)$ python setup.py develop
    (env)$ easy_install webtest

#. Let's extend ``unit_testing/tutorial/tests.py`` to include a
   functional test:

   .. literalinclude:: functional_testing/tutorial/tests.py
    :linenos:

#. Now run the tests:

   .. code-block:: bash


    (env)$ nosetests tutorial
    .
    ----------------------------------------------------------------------
    Ran 2 tests in 0.141s

    OK

Analysis
========

We now have the end-to-end testing we were looking for. WebTest lets us
simply extend our existing ``nose``-based test approach with functional
tests that are reported in the same output. These new tests not only
cover our templating, but they didn't dramatically increase the
execution time of our tests.

Extra Credit
============

#. Why do our functional tests use ``b''``?