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
|
:orphan:
tappy manual page
=================
Synopsis
--------
**tappy** [*options*] <*pathname*> [<*pathname*> ...]
Description
-----------
The :program:`tappy` command consumes the list of tap files
given as *pathname* s and produces an output similar to what
the regular text test-runner from python's :py:mod:`unittest`
module would. If *pathname* points to a directory,
:program:`tappy` will look in that directory for ``*.tap``
files to consume.
If you have a tool that consumes the `unittest` regular output,
but wish to use the TAP protocol to better integrate with other
tools, you may use tappy to *replay* tests from .tap files,
without having to actually run the tests again (which is much
faster).
It is also an example of how to use the tap consumer API
provided by the :py:mod:`tap` module.
.. warning::
:program:`tappy`'s output will differ from the standard
:py:mod:`unittest` output. Indeed it cannot reproduce error
and failure messages (e.g. stack traces, ...) that are not
recorded in tap files.
Options
-------
-h, --help show a short description and option list
and exit.
-v, --verbose produce verbose output
Author
------
The :program:`tappy` and the :py:mod:`tap` modules were written
by Matt LAYMAN (https://github.com/python-tap/tappy).
This manual page was written Nicolas CANIART, for the Debian project.
|
