freebsd-dev/lib/libarchive/test
Tim Kientzle 37320c7575 Overhaul of 'ar' support:
* use "AR_GNU" as the format name instead of AR_SVR4 (it's what everyone is going to call it anyway)
  * Simplify numeric parsing to unsigned (none of the numeric values should ever be negative); don't run off end of numeric fields.
  * Finish parsing the common header fields before the next I/O request (which might dump the contents)
  * Be smarter about format guessing and trimming filenames.
  * Most of the magic values are only used in one place, so just inline them.
  * Many more comments.
  * Be smarter about handling damaged entries; return something reasonable.
  * Call it a "filename table" instead of a "string table"
  * Update tests.

Enable selection of 'ar', 'arbsd', and 'argnu' formats by name
(this allows bsdtar to create ar format archives).

The 'ar' writer still needs some work; it should reject
entries that aren't regular files and should probably also
strip leading paths from filenames.
2007-04-14 22:34:10 +00:00
..
main.c Portability: Don't use mkdtemp() when mkdir() will suffice. 2007-04-14 05:17:06 +00:00
Makefile Conventionally, tar archives have always included a trailing '/' 2007-04-14 08:20:31 +00:00
README
test_acl_basic.c
test_acl_pax.c
test_archive_api_feature.c
test_bad_fd.c
test_read_data_large.c
test_read_extract.c
test_read_format_ar.c Overhaul of 'ar' support: 2007-04-14 22:34:10 +00:00
test_read_format_cpio_bin_bz2.c
test_read_format_cpio_bin_gz.c
test_read_format_cpio_bin_Z.c
test_read_format_cpio_bin.c
test_read_format_cpio_odc.c
test_read_format_cpio_svr4_gzip.c
test_read_format_cpio_svr4c_Z.c
test_read_format_empty.c
test_read_format_gtar_gz.c
test_read_format_iso_gz.c
test_read_format_isorr_bz2.c
test_read_format_pax_bz2.c
test_read_format_tar.c
test_read_format_tbz.c
test_read_format_tgz.c
test_read_format_tz.c
test_read_format_zip.c
test_read_large.c
test_read_position.c
test_read_truncated.c
test_tar_filenames.c Conventionally, tar archives have always included a trailing '/' 2007-04-14 08:20:31 +00:00
test_write_disk_perms.c Notice when mkdir() fails. 2007-03-24 05:02:16 +00:00
test_write_disk_secure.c
test_write_disk.c
test_write_format_ar.c Overhaul of 'ar' support: 2007-04-14 22:34:10 +00:00
test_write_format_cpio_empty.c
test_write_format_shar_empty.c
test_write_format_tar_empty.c
test_write_format_tar.c
test_write_open_memory.c
test.h Libarchive 2.0.23: 2007-03-11 10:29:52 +00:00

$FreeBSD$

This is the test harness for libarchive.

It compiles into a single program "libarchive_test" that is intended
to exercise as much of the library as possible.  It is, of course,
very much a work in progress.

Each test is a function named test_foo in a file named test_foo.c.
Note that the file name is the same as the function name.
Each file must start with this line:

  #include "test.h"

The test function must be declared with a line of this form

  DEFINE_TEST(test_foo)

Nothing else should appear on that line.

When you add a test, please update the Makefile to add your
file to the list of tests.  The Makefile and main.c use various
macro trickery to automatically collect a list of test functions
to be invoked.

Each test function can rely on the following:

  * The current directory will be a freshly-created empty directory
    suitable for that test.  (The top-level main() creates a
    directory for each separate test and chdir()s to that directory
    before running the test.)

  * The test function should use assert(), assertA() and similar macros
    defined in test.h.  If you need to add new macros of this form, feel
    free to do so.

  * You are encouraged to document each assertion with a failure() call
    just before the assert.  The failure() function is a printf-like
    function whose text is displayed only if the assertion fails.  It
    can be used to display additional information relevant to the failure:

       failure("The data read from file %s did not match the data written to that file.", filename);
       assert(strcmp(buff1, buff2) == 0);

  * Tests are encouraged to be economical with their memory and disk usage,
    though this is not essential.