Test Anything Protocol

Short description: Software testing protocol

For the network tunnel driver, see TUN/TAP.

The Test Anything Protocol (TAP) is a protocol for communicating between test logic, called a TAP producer, and a test harness in a language-agnostic way. Originally developed for unit testing of the Perl interpreter in 1987, producers and parsers are now available for many development platforms.

## Contents

* 1 History
* 2 Specification
* 3 Examples
* 4 See also
* 5 References
* 6 External links

## History

TAP was created for the first version of the Perl programming language (released in 1987), as part of Perl's core test harness (t/TEST). The `Test::Harness` module was written by Tim Bunce and Andreas König to allow Perl module authors to take advantage of TAP. It became the de facto standard for Perl testing.[1][2][3]

Development of TAP, including standardization of the protocol, writing of test producers and consumers, and evangelizing the language is coordinated at the TestAnything website.[4]

As a protocol which is agnostic of programming language, TAP unit testing libraries expanded beyond their Perl roots and have been developed for various languages and systems such as PostgreSQL,[5] MySQL,[6] JavaScript[7] and other implementations listed on the project site.[4] A TAP C library is included as part of the FreeBSD Unix distribution and is used in the system's regression test suite.[8]

## Specification

A formal specification for this protocol exists in the `TAP::Spec::Parser` and `TAP::Parser::Grammar` modules. The behavior of the `Test::Harness` module is the de facto TAP standard implementation, along with a writeup of the specification on TestAnything.org.[4]

A project to produce an IETF standard for TAP was initiated in August 2008, at YAPC::Europe 2008.[4][needs update]

## Examples

Here's an example of TAP's general format:

1..48
ok 1 Description # Directive
# Diagnostic
....
ok 47 Description
ok 48 Description

For example, a test file's output might look like:

1..4
ok 1 - Input file opened
not ok 2 - First line of the input valid.
More output from test 2. There can be
arbitrary number of lines for any output
so long as there is at least some kind
of whitespace at beginning of line.
ok 3 - Read the rest of the file
#TAP meta information
not ok 4 - Summarized correctly # TODO: not written yet

## See also

* xUnit

## References

1. ↑ "A Perl toolbox for regression tests : Testing Tools". https://nnc3.com/mags/LM10/Magazine/Archive/2005/61/076-080_perl/article.html. Retrieved 27 October 2017.
2. ↑ Schilli, Mike. "Print as Print Can » Linux Magazine". http://www.linux-magazine.com/Issues/2016/187/Perl-Print-Test. Retrieved 27 October 2017.
3. ↑ Szabo, Gabor. "TAP - Test Anything Protocol". https://perlmaven.com/tap-test-anything-protocol.
4. ↑ 4.0 4.1 4.2 4.3 "The Test Anything Protocol website". http://www.testanything.org/. Retrieved February 17, 2025.
5. ↑ McClive, Simon (2017-09-21). "Unit testing Postgres with pgTAP". https://medium.com/engineering-on-the-incline/unit-testing-postgres-with-pgtap-af09ec42795.
6. ↑ Gravelle, Rob (2012-08-13). "Testing Your MySQL Stored Procedures with MyTAP". https://www.databasejournal.com/features/mysql/testing-your-mysql-stored-procedures-with-mytap.html.
7. ↑ "Node Tap". https://node-tap.org/.
8. ↑ "TAP(3) manual page". https://www.freebsd.org/cgi/man.cgi?query=tap&sektion=3.

## External links

* No URL found. Please specify a URL here or add one to Wikidata.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Test Anything Protocol. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Test_Anything_Protocol&oldid=3988738"