x/swiftonhpss
Code Issues Proposed changes

Functional test setup steps for developers guide

Browse Source 
Change-Id: I86c562d555c402a5e3ce3ce471a40d872de8bdce
Signed-off-by: Chetan Risbud <crisbud@redhat.com>
Reviewed-on: http://review.gluster.org/5292
Reviewed-by: Luis Pabon <lpabon@redhat.com>
Tested-by: Luis Pabon <lpabon@redhat.com>
This commit is contained in:
Chetan Risbud 2013-07-05 13:30:25 +05:30 committed by Luis Pabon
parent 9f7956e40b
commit 7575c3cc01
1 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/markdown/dev_guide.md
View File

@ -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: