diff options
authorChetan Risbud <>2013-07-05 13:30:25 +0530
committerLuis Pabon <>2013-07-09 12:47:33 -0700
commit7575c3cc0150ac9440b21da3c82aba677497618a (patch)
parent9f7956e40b195774d5c8f90d242405d0930b6888 (diff)
Functional test setup steps for developers guide
Change-Id: I86c562d555c402a5e3ce3ce471a40d872de8bdce Signed-off-by: Chetan Risbud <> Reviewed-on: Reviewed-by: Luis Pabon <> Tested-by: Luis Pabon <>
1 files changed, 16 insertions, 2 deletions
diff --git a/doc/markdown/ b/doc/markdown/
index 0fb776d..52dcf01 100644
--- a/doc/markdown/
+++ b/doc/markdown/
@@ -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.
+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
+4) Volumes should be mounted under "/mnt/gluster-object/test" and
+"/mnt/gluster-object/test2" respectively.
+####To run functional tests:
### Commiting changes
After making the changes needed, you can commit your changes by typing: