glusterfs/tests
Krutika Dhananjay 6556b5cf40 glusterd: delete "volume-name" from dict before processing the next option
Change-Id: Ib78963c1f43a66dab50b443742979c7c4e4cbc23
BUG: 958790
Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
Reviewed-on: http://review.gluster.org/4940
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2013-05-02 10:58:20 -07:00
..
basic build: sync glusterfs.spec.in with Fedora glusterfs.spec 2013-04-26 02:38:07 -07:00
bugs glusterd: delete "volume-name" from dict before processing the next option 2013-05-02 10:58:20 -07:00
performance performance/open-behind: use anonymous fd for doing fstat and readv 2013-02-19 16:07:21 -08:00
utils glusterd, cli: Task id's for async tasks 2012-12-19 13:32:49 -08:00
afr.rc cluster/afr: Avoid self-healing extended attribute used by SELinux. 2013-04-30 20:11:37 -07:00
cluster.rc tests/cluster.rc: support for virtual multi-server glusterd tests 2013-02-26 09:07:13 -08:00
dht.rc cluster/distribute: Ignore non-participating subvols for layout checks 2013-04-09 12:49:40 -07:00
fileio.rc tests/fileio.rc: library for file descriptor based IO in tests 2013-02-21 23:26:57 -08:00
include.rc build: sync glusterfs.spec.in with Fedora glusterfs.spec 2013-04-26 02:38:07 -07:00
README tests/README: add a note about usage of 'mount -t glusterfs' 2012-11-29 22:01:25 -08:00
volume.rc tests: Fix volume-status test script 2013-04-19 01:55:36 -07:00

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/* !!!