This page has information about standardizing the test output format.  Having a standardized format would
allow for simpler processing by test harnesses which collected, aggregated and presented the results from
multiple kselftest tests.

It was strongly recommended, in the 2014 kernel summit, to avoid creating a new test format.  In that meeting,
Tim Bird recommended Jenkins output format, but Tim now recommends using the TAP format, and including integrating libtap into the kernel source tree.

=== Some TAP resources and information ===
  * Test Anything Protocol ([[http://testanything.org/|main website]]) ([[http://en.wikipedia.org/wiki/Test_Anything_Protocol|Wikipedia entry]])
  * libtap (C library to produce TAP output) - http://ccodearchive.net/info/tap.html
  * bash-tap-functions (bash functions to produce TAP output) - https://github.com/goozbach/bash-tap-functions

== TAP version 14 ==

The effort to create TAP version 14 has stalled.

Version 14 was intended to capture current practices that are already in use.

The pull request for version 14, and resulting discussion is at:

  * https://github.com/TestAnything/testanything.github.io/pull/36/files

You can see the full version 14 document in the submitter's repo:

  $ git clone https://github.com/isaacs/testanything.github.io.git
  $ cd testanything.github.io
  $ git checkout tap14
  $ ls tap-version-14-specification.md
  
== TAP can be read by multiple test harnesses == 
While a test harness is outside the current scope of kselftest, some people may want to use one of the
many (many!) test harnesses that can process TAP output:
  * C TAP Harness (program to consume and process TAP output) - http://www.eyrie.org/~eagle/software/c-tap-harness/readme.html
  * Jenkins plugin - https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin