./devel/py-pycotap, Tiny test runner that outputs TAP results to standard output

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 1.2.2nb1, Package name: py310-pycotap-1.2.2nb1, Maintainer: pkgsrc-users

pycotap is a simple Python test runner for unittest that outputs
Test Anything Protocol results directly to standard output.

Contrary to other TAP runners for Python, pycotap:

* prints TAP (and only TAP) to standard output instead of to
a separate file, allowing you to pipe it directly to TAP pretty
printers and processors (such as the ones listed on the tape
page). By piping it to other consumers, you can avoid the need
to add specific test runners to your test code. Since the TAP
results are printed as they come in, the consumers can directly
display results while the tests are run.
* only contains a TAP reporter, so no parsers, no frameworks,
no dependencies.
* is configurable: you can choose how you want the test output
and test result diagnostics to end up in your TAP output (as
TAP diagnostics, YAML blocks, or attachments). The defaults
are optimized for a Jenkins based flow.

Master sites:

Filesize: 6.264 KB

Version history: (Expand)

CVS history: (Expand)


   2022-01-04 21:55:40 by Thomas Klausner | Files touched by this commit (1595) 
Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS
   2022-01-04 07:53:58 by Thomas Klausner | Files touched by this commit (2) 
Log message:
py-pycotap: fix PLIST for python != 3.9
   2022-01-03 11:51:31 by Thomas Klausner | Files touched by this commit (1) 
Log message:
py-pycotap: cleanup
   2022-01-03 11:49:10 by Thomas Klausner | Files touched by this commit (4) 
Log message:
devel/py-pycotap: import py-pycotap-1.2.2

pycotap is a simple Python test runner for unittest that outputs
Test Anything Protocol results directly to standard output.

Contrary to other TAP runners for Python, pycotap:

    * prints TAP (and only TAP) to standard output instead of to
    a separate file, allowing you to pipe it directly to TAP pretty
    printers and processors (such as the ones listed on the tape
    page). By piping it to other consumers, you can avoid the need
    to add specific test runners to your test code. Since the TAP
    results are printed as they come in, the consumers can directly
    display results while the tests are run.
    * only contains a TAP reporter, so no parsers, no frameworks,
    no dependencies.
    * is configurable: you can choose how you want the test output
    and test result diagnostics to end up in your TAP output (as
    TAP diagnostics, YAML blocks, or attachments). The defaults
    are optimized for a Jenkins based flow.