kinow/gtest-tap-listener

GoogleTest TAP Listener

GTest TAP Listener

Overview

This is a small contribution to Google Test. Oliver and I were working on an issue in Jenkins plug-in when he told me about Google Test. As this plug-in relies heavily on TAP, we talked about how it looked like a good idea have TAP in GoogleTest.

Although GoogleTest has an XML writer, it lacks a TAP one. Using its Event Listeners model it was quite easy to implement this first version of this TAP listener.

See the examples directory for code to be used as reference.

Write to stdout

By default, the GoogleTest TAP Listener emits TAP to files with names that match the test names. If you prefer to have the output written to stdout, use the definition GTEST_TAP_PRINT_TO_STDOUT when compiling your project.

Changelog

See CHANGES.md.

Contributions

Feel free to send contributions, pull requests, suggestions or any other feedback to the project.

See CONTRIBUTING.md.

Authors

A list of contributors to this repository can be found in CONTRIBUTORS.txt.

Links

• https://github.com/kinow/gtest-tap-listener
• https://github.com/google/googletest
• https://tupilabs.com/tap4j/

License

Licensed under MIT. See LICENSE.txt.

gtest-tap-listener's Issues

prefix for .tap filename

Hi,
Could you please add:

• configurable prefix for filename generated by tap.h
• Location where to store .tap files?

The use-case is as following:

• we run gtest 2-3 time:
• w/ valgringd
• w/ code coverage
• just gtest

Every execution overrides .tap files created on previous step.

The proposal:

% GTEST_TAP_FILENAME_PREFIX="gtest_vg_" valgrind gtest
% GTEST_TAP_FILENAME_PREFIX="gtest_codecov_" codecov gtest
% GTEST_TAP_DIR=/tmp/taps gtest

Thanks

const qualifier applied to void return type.

The function addTapTestResult is declared with a return type of const void. This has no effect and trips up -Wignored-qualifiers in clang

Write to stdout rather that a file on disk

From a quick look through the implementation, it appears that it writes to files on disk rather than stdout. Is that understanding correct?

TAP expects output to be written to standard output:
http://testanything.org/tap-version-14-specification.html

(for example, the "Bail out!" section talks specifically about writing to standard output)

Does GoogleTest have an option for not writing its own output to standard output, so that the TAP listener could write there instead, per the TAP spec?

Write to TAP stream during execution

From a quick look at the code, it appears that tap.h currently holds all results until the test run completes, and then writes to output then. Is that understanding correct?

If so, I believe that conflicts with how TAP is designed to work, as a stream, with results written while tests are running:
http://testanything.org/philosophy.html

Can the implementation be changed to stream output, rather than buffering it and writing at the end?