deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
gitolite/t
History
Sitaram Chamarty 44e6bc4bb2 logging (but see below) 
The logging is both for paranoia and parsing/automated processing.  The
ones you're probably interested in parsing should be easy to pick out
and are very likely to have tab-delimited fields already.
2012-03-24 10:30:43 +05:30
..
keys ssh-basic tests (and that's all we will ever do; see below) 2012-03-24 10:30:42 +05:30
access.t (!!) neat little 'access' command... 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 info command deals with groups 2012-03-24 10:30:42 +05:30
listers.t new test 'listers' 2012-03-24 10:30:42 +05:30
personal-branches.t (!!) personal branches -- 1 line of code, 50 lines of test! 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 changes to custom command invocation etc.; see below 2012-03-24 10:30:43 +05:30
ssh-basic.t logging (but see below) 2012-03-24 10:30:43 +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
z-end.t minor changes to the testing infrastructure 2012-03-24 10:30:43 +05:30

README 

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.