path: root/tests/README
Commit message (Collapse)AuthorAgeFilesLines
* tests: Create a regression-tests package for distributionHarshavardhana2013-09-191-26/+0
| | | | | | | | | | | | | | | | As of today regression tests are an in-house breed, by making it a new package and distributing it ensures larger set of people use it and contribute to it. This can also be used by any consumer/user to build their own environment for glusterfs regression testing which is today limited only to 'upstream' 'glusterfs' releases and Change-Id: I4f7e9fd1c49982dcf0d788ef6a83ffe895a956ac BUG: 764966 Signed-off-by: Harshavardhana <> Reviewed-on: Reviewed-by: Niels de Vos <> Tested-by: Gluster Build System <>
* tests/README: add a note about usage of 'mount -t glusterfs'Amar Tumballi2012-11-291-2/+8
| | | | | | | | Change-Id: Ic9e02c34e8d7c8eb4a18c459d2a8899d85a59189 Signed-off-by: Amar Tumballi <> Reviewed-on: Reviewed-by: Anand Avati <> Tested-by: Anand Avati <>
* tests: pre-commit regression testsAnand Avati2012-10-181-0/+20
Framework for writing test cases to be submitted with patches. This framework and the test cases get exercised by Jenkins in the pre-commit regression test. Jenkins is configured to give a +1 verified vote only if the regression test passes without failures (which includes test cases added/changed by the patch being tested) Every patch should include a test case (either extensions/changes to existing test cases or add new ones, as appropriate). The test case should be part of the same commit so that both code and test case get reviewed together. Test cases added are cumulative. Every new patch gets tested against its own test case and every test case previously added. A lot of new commits in the near future will be pure test cases (with no code change) which will get added in "catch up" mode. The tool used for implementing test cases is 'prove', and the framework itself is modeled similar to the POSIX compliance filesystem test suite. Under the top level directory, a new directory named 'tests/' is added. This contains top level classifier directories and framework files/scripts. Functionality tests should be created under a classifier directory below 'tests/'. For e.g: tests/basic/mount.t tests/performance/write-behind.t Bugs which get fixed should include a test case script named by the bug id, so that we are guaranteed any new change will not bring the issue back. For e.g: tests/bugs/bug-123456.t Triggering of regression tests in Jenkins is manual at this point as we do not want the entire test suite to run against every revision of a patch while it is still in the review/resubmit cycle. Signed-off-by: Anand Avati <> Change-Id: I8078244619135ccaba38e068925f8ca85141055a BUG: 764966 Signed-off-by: Anand Avati <> Reviewed-on: Tested-by: Gluster Build System <>