view release on metacpan or  search on metacpan

t/data/generate/c-tap-harness/output/readme  view on Meta::CPAN

        tests_libtap_c_basic_LDADD = tests/tap/libtap.a

    and add them to check_PROGRAMS.  If you include the float.c add-on in
    your libtap library, you will need to add -lm to the _LDADD setting
    for all test programs linked against it.

    A more complex example from the remctl package that needs additional
    libraries:

        tests_client_open_t_LDFLAGS = $(GSSAPI_LDFLAGS)
        tests_client_open_t_LDADD = client/libremctl.la tests/tap/libtap.a \
                util/libutil.la $(GSSAPI_LIBS)

    If the test program doesn't need to be compiled, add it to EXTRA_DIST
    so that it will be included in the distribution.

  * If you have test programs written in shell, copy tests/tap/libtap.sh
    the tap subdirectory of your tests directory and add it to EXTRA_DIST.
    Shell programs should start with:

        . "${C_TAP_SOURCE}/tap/libtap.sh"

    and can then use the functions defined in the library.

  * Optionally copy docs/writing-tests into your package somewhere, such
    as tests/README, as instructions to contributors on how to write tests
    for this framework.

  If you have configuration files that the user must create to enable some
  of the tests, conventionally they go into tests/config.

  If you have data files that your test cases use, conventionally they go
  into tests/data.  You can then find the data directory relative to the
  C_TAP_SOURCE environment variable (set by runtests) in your test
  program.  If you have data that's compiled or generated by Autoconf, it
  will be relative to the BUILD environment variable.  Don't forget to add
  test data to EXTRA_DIST as necessary.

  For more TAP library add-ons, generally ones that rely on additional
  portability code not shipped in this package or with narrower uses, see
  the rra-c-util package [1].  There are several additional TAP library
  add-ons in the tests/tap directory in that package.  It's also an
  example of how to use this test harness in another package.

  [1] https://www.eyrie.org/~eagle/software/rra-c-util/

SUPPORT

  The C TAP Harness web page at:

      https://www.eyrie.org/~eagle/software/c-tap-harness/

  will always have the current version of this package, the current
  documentation, and pointers to any additional resources.

  For bug tracking, use the issue tracker on GitHub:

      https://github.com/rra/c-tap-harness/issues

  Please be aware that I tend to be extremely busy and work projects often
  take priority.  I'll save your report and get to it as soon as I can,
  but it may take me a couple of months.

SOURCE REPOSITORY

  C TAP Harness is maintained using Git.  You can access the current
  source on GitHub at:

      https://github.com/rra/c-tap-harness

  or by cloning the repository at:

      https://git.eyrie.org/git/devel/c-tap-harness.git

  or view the repository via the web at:

      https://git.eyrie.org/?p=devel/c-tap-harness.git

  The eyrie.org repository is the canonical one, maintained by the author,
  but using GitHub is probably more convenient for most purposes.  Pull
  requests are gratefully reviewed and normally accepted.

LICENSE

  The C TAP Harness package as a whole is covered by the following
  copyright statement and license:

    Copyright 2000-2001, 2004, 2006-2016 Russ Allbery <eagle@eyrie.org>
    Copyright 2006-2009, 2011-2013
        The Board of Trustees of the Leland Stanford Junior University

    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:

    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
    IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
    CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
    TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
    SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

  Some files in this distribution are individually released under
  different licenses, all of which are compatible with the above general
  package license but which may require preservation of additional
  notices.  All required notices, and detailed information about the
  licensing of each file, are recorded in the LICENSE file.

  Files covered by a license with an assigned SPDX License Identifier
  include SPDX-License-Identifier tags to enable automated processing of
  license information.  See https://spdx.org/licenses/ for more
  information.