diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 31 |
1 files changed, 28 insertions, 3 deletions
diff --git a/README.md b/README.md index 1cab5c19390..9d68e033782 100644 --- a/README.md +++ b/README.md @@ -3,15 +3,40 @@ petabytes. It provides interfaces for object, block and file storage. ## Development - Contributions to gluster in the form of patches and new feature additions can - be made by following steps outlined at [Developers Guide](https://gluster.readthedocs.io/en/latest/Developer-guide/Developers-Index/#contributing-to-the-gluster-community). + The development workflow is documented in [Contributors guide](CONTRIBUTING.md) ## Documentation - The Gluster documentation can be found at [Gluster Docs](http://gluster.readthedocs.io/en/latest). + The Gluster documentation can be found at [Gluster Docs](http://docs.gluster.org). ## 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. |