Metadata-Version: 2.2
Name: pycotap
Version: 1.3.1
Summary: A tiny test runner that outputs TAP results to standard output.
Home-page: https://github.com/remko/pycotap
Author: Remko Tronçon
Author-email: 08cage-calm@icloud.com
License: MIT
Keywords: tap unittest testing
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Topic :: Utilities
Classifier: License :: OSI Approved :: MIT License
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: Software Development :: Testing
License-File: COPYING
Dynamic: author
Dynamic: author-email
Dynamic: classifier
Dynamic: description
Dynamic: home-page
Dynamic: keywords
Dynamic: license
Dynamic: summary


`pycotap` is a simple Python test runner for ``unittest`` that outputs 
`Test Anything Protocol <http://testanything.org>`_ 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 <https://www.npmjs.com/package/tape#pretty-reporters>`_). 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 <http://jenkins-ci.org>`_ based
  flow.

Documentation and examples can be found on `the pycotap page 
<https://github.com/remko/pycotap>`_.
