Extensive improvements to the libarchive_test test program that

exercises and verifies the libarchive APIs:

* Improved error reporting; hexdumps are now provided for
  many file/memory content differences.
* Overall status more clearly counts "tests" and "assertions"
* Reference files can now be stored on disk instead of having
  to be compiled into the test program itself.  A couple of
  tests have been converted to this more natural structure.
* Several memory leaks corrected so that leaks within libarchive
  itself can be more easily detected and diagnosed.
* New test: GNU tar compatibility
* New test: Zip compatibility
* New test: Zero-byte writes to a compressed archive entry
* New test: archive_entry_strmode() format verification
* New test: mtree reader
* New test: write/read of large (2G - 1TB) entries to tar archives
  (thanks to recent performance work, this test only requires a few seconds)
* New test: detailed format verification of cpio odc and newc writers
* Many minor additions/improvements to existing tests as well.

1 files changed, 10 insertions, 2 deletions

diff --git a/lib/libarchive/test/README b/lib/libarchive/test/README
index 011aa8e..0190b7c 100644
--- a/lib/libarchive/test/README
+++ b/lib/libarchive/test/README
@@ -32,7 +32,11 @@ Each test function can rely on the following:
 
   * 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.
+    free to do so.  The current macro set includes assertEqualInt() and
+    assertEqualString() that print out additional detail about their
+    arguments if the assertion does fail.  'A' versions also accept
+    a struct archive * and display any error message from there on
+    failure.
 
   * You are encouraged to document each assertion with a failure() call
     just before the assert.  The failure() function is a printf-like
@@ -43,7 +47,10 @@ Each test function can rely on the following:
        assert(strcmp(buff1, buff2) == 0);
 
   * Tests are encouraged to be economical with their memory and disk usage,
-    though this is not essential.
+    though this is not essential.  The test is occasionally run under
+    a memory debugger to try to locate memory leaks in the library;
+    as a result, tests should be careful to release any memory they
+    allocate.
 
   * Disable tests on specific platforms as necessary.  Please don't
     use config.h to adjust feature requirements, as I want the tests
@@ -53,3 +60,4 @@ Each test function can rely on the following:
 #if !defined(__PLATFORM) && !defined(__Platform2__)
     assert(xxxx)
 #endif
+