deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Bailout tests unless envvar $GITOLITE_TEST is 'y'

Browse source 
[committer made some changes to t/README]
This commit is contained in:
Olof Johansson 2012-08-09 18:02:00 +02:00 committed by Sitaram Chamarty
parent 31166e1e1c
commit ba67f6f9ca
2 changed files with 15 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/lib/Gitolite/Test.pm
View file

@ -37,6 +37,12 @@ use warnings;
# ---------------------------------------------------------------------- # ----------------------------------------------------------------------
# make sure the user is ready for it
if (not $ENV{GITOLITE_TEST} or $ENV{GITOLITE_TEST} ne 'y') {
print "Bail out! See t/README for information on how to run the tests.\n";
exit 255;
}
# required preamble for all tests # required preamble for all tests
try " try "
DEF gsh = /TRACE: gsh.SOC=/ DEF gsh = /TRACE: gsh.SOC=/

13
t/README
View file

@ -1,8 +1,13 @@
============================================
WARNING: THE TEST SUITE DELETES STUFF FIRST! WARNING: THE TEST SUITE DELETES STUFF FIRST!
============================================
Testing gitolite3 is now one command after the clone: Please run the tests ONLY on a userid where it's ok to LOSE DATA.
prove On such a userid, clone gitolite then run this command in the clone:
But because it starts by cleaning the slate, it's best to do it on a spare GITOLITE_TEST=y prove
userid that you are ok to lose data on.
http://sitaramc.github.com/gitolite/testing.html has more details. It will
also help you try out gitolite if you want to go beyond just the test suite.