aboutsummaryrefslogtreecommitdiffstats
path: root/pathod/templates/docs_test.html
blob: ecd84bc7a37ef816cbbd2ad7505a4b1814e670d1 (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
{% extends "docframe.html" %} {% block body %}
<div class="page-header">
    <h1>
        pathod.test
        <small>Using pathod in unit tests.</small>
    </h1>
</div>

<p>The <b>pathod.test</b> module is a light, flexible testing layer for HTTP clients.
    It works by firing up a Pathod instance in a separate thread, letting you use
    Pathod's full abilities to generate responses, and then query Pathod's internal
    logs to establish what happened. All the mechanics of startup, shutdown, finding
    free ports and so forth are taken care of for you.
</p>

<p>The canonical docs can be accessed using pydoc: </p>

<pre class="terminal">pydoc pathod.test</pre>

<p>
    The remainder of this page demonstrates some common interaction patterns using
    <a href="http://nose.readthedocs.org/en/latest/">nose</a>. These examples are
    also applicable with only minor modification to most commonly used Python testing
    engines.
</p>

<section>
    <div class="page-header">
        <h1>Context Manager</h1>
    </div>

    {% include "examples_context.html" %}
</section>

<section>
    <div class="page-header">
        <h1>One instance per test</h1>
    </div>

    {% include "examples_setup.html" %}
</section>

<section>
    <div class="page-header">
        <h1>One instance per suite</h1>
    </div>

    {% include "examples_setupall.html" %}
</section>
{% endblock %}