The UnifyFS examples are being used as integration tests with continuous integration tools. These scripts depend on sharness which is set up in the containing directory (UnifyFS/t/) and may not function properly if moved.

The numbered scripts are the setup and tests being run by RUN_CI_TESTS.sh.

001-setup.sh : Checks for an installation of UnifyFS and sets up variables needed for testing.

002-start-server.sh : Starts unifyfsd and tests to ensure it is running.

100-900 : Scripts for testing the examples.

990-stop-server.sh : Stops unifyfsd and cleans up.

The other scripts (ci-functions.sh, setup-lsf.sh, and setup-slurm.sh) contain helper functions and variables used by the tests. Full details can be found in UnifyFS testing documentation.

In order to run these scripts, make sure you are either submitting a batch job to run them, or are first in an interactive allocation.

Note: mpirun is currently not supported but coming soon.

To run all of the tests, simply run ./RUN_CI_TESTS.sh.

E.g.:

$ ./RUN_CI_TESTS.sh

or

$ prove -v RUN_CI_TESTS.sh

In order to run individual tests, source the 001-setup.sh script first, followed by 002-start-server.sh. Then source each desired script after that preceded by $CI_DIR. When finished, source the 990-stop-server.sh script last.

E.g.:

$ . full/path/to/001-setup.sh
$ . $CI_DIR/002-start-server.sh
$ . $CI_DIR/100-writeread-tests.sh
$ . $CI_DIR/990-stop-server.sh

If additional tests are desired, create a script after the fashion of 100-writeread-tests.sh where the prefixed number indicates the desired order for running the tests. Then source that script in RUN_CI_TESTS.sh in the desired order.

There are environment variables that can be set to change the default behavior of this testing suite. See our testing guide for a full list.

See our Testing Guide for full documentation on writing and adding additional tests.