selftests: clean up how the helper function files are found by the tests

Allow selftests to be run without making assumptions about the current
directory.  The documentation currently states that they can be run
with the current directory being the selftests directory, in which
case they might be run as (for example) "./appliance" or in the
top-level directory, in which case they would be run as

Signed-off-by: Theodore Ts'o <>

The selftests can be run out of the top-level directory via
./selftests/<test-script>, e.g., ./selftests/appliance, or out of the
selftests directory, so they would be run via "./appliance".
4 files changed
tree: e85c53f46c53150ede079e98d422916b266939ed
  1. Documentation/
  2. fstests-bld/
  3. kernel-build/
  4. release/
  5. run-fstests/
  6. selftests/
  7. test-appliance/
  8. .checkpatch.conf
  9. .dockerignore
  10. .gitignore
  11. .travis.yml
  12. build-appliance
  13. config
  15. Dockerfile
  16. Makefile
  18. setup-buildchroot


The xfstests-bld project was originally designed as system to make it easy to build xfstests in way that isolated it from the versions of various libraries such as libaio, xfsprogs, that were available in a particular distribution. It has since evolved to have four primary functions:

More details about how to use xfstests-bld to carry out these three functions can be found in the Documentation directory.

If you are first getting started using xfstests, you should probably read the Quickstart guide first. If you don't know much about xfstests, you may also want to read this introduction to xfstests.


The xfstests-bld project has been made available under the terms of the GNU General Public License, version 2. A copy can be found in the file named COPYING in the distribution.