andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README: add a section for giving hints on testing

Browse Source 
Change-Id: I1529494504c38172f56759c0f06231864e32df24
updates: bz#1193929
Signed-off-by: Amar Tumballi <amarts@redhat.com>
This commit is contained in:
Amar Tumballi 2018-09-24 10:31:23 +05:30
parent 46b970f64a
commit 4511435fd3
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -12,6 +12,32 @@
## Deployment
Quick instructions to build and install can be found in [INSTALL](INSTALL) file.
## Testing
GlusterFS source contains some functional tests under `tests/` directory. All
these tests are run against every patch submitted for review. If you want your
patch to be tested, please add a `.t` test file as part of your patch submission.
You can also submit a patch to only add a `.t` file for the test case you are
aware of.
To run these tests, on your test-machine, just run `./run-tests.sh`. Don't run
this on a machine where you have 'production' glusterfs is running, as it would
blindly kill all gluster processes in each runs.
If you are sending a patch, and want to validate one or few specific tests, then
run a single test by running the below command.
```
bash# /bin/bash ${path_to_gluster}/tests/basic/rpc-coverage.t
```
You can also use `prove` tool if available in your machine, as follows.
```
bash# prove -vmfe '/bin/bash' ${path_to_gluster}/tests/basic/rpc-coverage.t
```
## Maintainers
The list of Gluster maintainers is available in [MAINTAINERS](MAINTAINERS) file.