4579609e33
Change-Id: I050d01b01eac46550aa435da7d96a972e0393d35 BUG: 770655 Signed-off-by: Avra Sengupta <asengupt@redhat.com> Reviewed-on: http://review.gluster.org/4561 Reviewed-by: Jeff Darcy <jdarcy@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> |
||
---|---|---|
.. | ||
basic | ||
bugs | ||
performance | ||
utils | ||
cluster.rc | ||
dht.rc | ||
fileio.rc | ||
include.rc | ||
README | ||
volume.rc |
How to use test script framework. ================================= - Build and install the version of glusterfs with your changes. Make sure the installed version is accessible from $PATH. - To mount glusterfs, NEVER use 'mount -t glusterfs', instead use 'glusterfs -s ' method. This is because with the patch build setup doesnot install the /sbin/mount.glusterfs necessary, where as the glusterfs binary will be accessible with $PATH, and will pick the right version. - (optional) Set environment variables to specify location of export directories and mount points. Unless you have special requirements, the defaults should just work. The variables themselves can be found at the top of tests/include.rc. All of them can be overriden with environment variables. - Execute run-tests.sh in the top level directory as root. - If some test cases fail, you can execute the failed test case script directly bypassing run-tests.sh. At this time it might be useful to set the envrionment variable DEBUG=1 before running the individual test script directly by hand. - BE WARNED THAT THE TEST CASES DELETE /var/lib/glusterd/* !!!