mirror of
https://github.com/RsyncProject/rsync.git
synced 2026-03-17 22:06:42 -04:00
e553d27f41
previously built into Phil's test was clashing with the runtests.sh framework. I think one of the core problems might be that scripts which don't explicitly "exit 0" have return codes which vary depending on the particular shell. (c.f. the autoconf portability guide.) This might break the Debian test suite but I'm afraid I don't know enough about how it works yet. Hopefully eventually it can become just a wrapper around our 'make check'.
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 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/.