From 7575c3cc0150ac9440b21da3c82aba677497618a Mon Sep 17 00:00:00 2001 From: Chetan Risbud Date: Fri, 5 Jul 2013 13:30:25 +0530 Subject: Functional test setup steps for developers guide Change-Id: I86c562d555c402a5e3ce3ce471a40d872de8bdce Signed-off-by: Chetan Risbud Reviewed-on: http://review.gluster.org/5292 Reviewed-by: Luis Pabon Tested-by: Luis Pabon --- doc/markdown/dev_guide.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/markdown/dev_guide.md b/doc/markdown/dev_guide.md index 0fb776d..52dcf01 100644 --- a/doc/markdown/dev_guide.md +++ b/doc/markdown/dev_guide.md @@ -108,8 +108,22 @@ where *ENV* is either `py27` for systems with Python 2.7+, or `py26` for systems with Python 2.6+. #### Functional Tests -Fuctional tests are used to test a running Gluster for Swift environment. -**TBD**. +To run the functional tests the following requirements must be met. + +1) "/etc/swift" must not exist. So that test would not interfere with +existing setup. Functional test would create "/etc/swift" and populate +it with necessary configuration files. +2) User need to have administrative access. +2) "/mnt/gluster-object" directory must be created. +3) Volumes named "test", "test2" should be created. (Gluster volume / XFS +volume) +4) Volumes should be mounted under "/mnt/gluster-object/test" and +"/mnt/gluster-object/test2" respectively. + +####To run functional tests: +~~~ +tools/functional_tests.sh +~~~ ### Commiting changes After making the changes needed, you can commit your changes by typing: -- cgit