Philippe Coval 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
..
00-hello.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
README.testsuite 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
acls.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
backup.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
batch-mode.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
chgrp.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
chmod-option.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
chmod-temp-dir.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
chmod.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
chown.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
compare-dest.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
daemon-gzip-download.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
daemon-gzip-upload.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
daemon.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
default-acls.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
delete.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
devices.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
dir-sgid.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
duplicates.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
exclude.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
executability.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
files-from.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
fuzzy.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
hands.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
hardlinks.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
itemize.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
longdir.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
merge.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
missing.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
relative.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
rsync.fns 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
ssh-basic.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
symlink-ignore.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
trimslash.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
unsafe-byname.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
unsafe-links.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
wildmatch.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden
xattrs.test 2558f5de19 Imported Upstream version 3.0.8 13 jaren geleden

README.testsuite

automatic testsuite for rsync -*- text -*-

We're trying to develop some more substantial tests to prevent rsync
regressions. Ideally, all code changes or bug reports would come with
an appropriate test suite.

You can run these tests by typing "make check" in the build directory.
The tests will run using the rsync binary in the build directory, so
you do not need to do "make install" first. Indeed, you probably
should not install rsync before running the tests.

If you instead type "make installcheck" then the suite will test the
rsync binary from its installed location (e.g. /usr/local/bin/rsync).
You can use this to test a distribution build, or perhaps to run a new
test suite against an old version of rsync. Note that in accordance
with the GNU Standards, installcheck does not look for rsync on the
path.

If the tests pass, you should see a report to that effect. Some tests
require being root or some other precondition, and so will normally not
be checked -- look at the test scripts for more information.

If the tests fail, you will see rather more output. The scratch
directory will remain in the build directory. It would be useful if
you could include the log messages when reporting a failure.

These tests also run automatically on the build farm, and you can see
the results on http://build.samba.org/.