c7baba5363
Change-Id: Ic9e02c34e8d7c8eb4a18c459d2a8899d85a59189 Signed-off-by: Amar Tumballi <amarts@redhat.com> Reviewed-on: http://review.gluster.org/4249 Reviewed-by: Anand Avati <avati@redhat.com> Tested-by: Anand Avati <avati@redhat.com>
27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
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/* !!!
|