gitolite/t
Sitaram Chamarty 4e25a8acd1 ssh-basic tests (and that's all we will ever do; see below)
ssh tests are meant to ensure that basic authENTICATION is happening.
AuthORISATION is checked all over the rest of the test suite and these
two are quite orthogonal operations so there is no need to test all of
authZ with ssh.
2012-03-24 10:30:42 +05:30
..
keys ssh-basic tests (and that's all we will ever do; see below) 2012-03-24 10:30:42 +05:30
basic.t (test) forgot to set user.email/name to the standard value 2012-03-24 10:30:41 +05:30
gitolite-receive-pack install/test made easy (WARNING: read below) 2012-03-24 10:30:41 +05:30
gitolite-upload-pack install/test made easy (WARNING: read below) 2012-03-24 10:30:41 +05:30
glt 'info' command, plus lots more changes: 2012-03-24 10:30:42 +05:30
include-subconf.t more tests 2012-03-24 10:30:42 +05:30
info.t more tests 2012-03-24 10:30:42 +05:30
README install/test made easy (WARNING: read below) 2012-03-24 10:30:41 +05:30
reset ssh-authkeys done! 2012-03-24 10:30:42 +05:30
ssh-authkeys.t ssh-authkeys done! 2012-03-24 10:30:42 +05:30
ssh-basic.t ssh-basic tests (and that's all we will ever do; see below) 2012-03-24 10:30:42 +05:30
vrefs-1.t COUNT VREF and tests 2012-03-24 10:30:42 +05:30
vrefs-2.t COUNT VREF and tests 2012-03-24 10:30:42 +05:30

WARNING: THE TEST SUITE DELETES STUFF FIRST!

Testing gitolite3 is now one command after the clone:

    prove

But because it starts by cleaning the slate, it's best to do it on a spare
userid that you are ok to lose data on.