path: root/
Commit message (Collapse)AuthorAgeFilesLines
* tests: take regression tests out of autotoolsAnand Avati2013-09-201-0/+30
| | | | | | | | | | | | make "location independent" and replace 'make install' with cpio in Change-Id: I140473c7f558e1e0af93a863b79098ced516a76b BUG: 764966 Signed-off-by: Anand Avati <> Reviewed-on: Reviewed-by: Harshavardhana <> Tested-by: Gluster Build System <>
* tests: Create a regression-tests package for distributionHarshavardhana2013-09-191-3/+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: Print the actual, expected values for EXPECTPranith Kumar K2012-12-181-1/+1
| | | | | | | | | Change-Id: I394d23c0ea15bd340041550660cc5def017b5f15 BUG: 764966 Signed-off-by: Pranith Kumar K <> Reviewed-on: Tested-by: Gluster Build System <> Reviewed-by: Anand Avati <>
* Tests: Print elapsed time per test filePranith Kumar K2012-12-171-1/+1
| | | | | | | | | Change-Id: I61f7653bec357ec2b49d5b7719e564c31c2addbf BUG: 764966 Signed-off-by: Pranith Kumar K <> Reviewed-on: Tested-by: Gluster Build System <> Reviewed-by: Anand Avati <>
* tests: pre-commit regression testsAnand Avati2012-10-181-0/+3
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 <>