fbb9dafbd1
sometimes I want to quickly test a few lines of change within the context of
a currently-running/just-ran test, *without* doing the rollback etc.
Here's how you do that now:
- in your source tree, make the change and then run:
cp -a src hooks contrib/adc /some/tmp/place
- go to the tester userid and re-run your tests like so:
GQT=/some/tmp/place ./test-driver.sh
it'll rollback as normal then overwrite src and hooks from $GQT
Also, there's now a "dbg" sub that can be used for quick printf-style
debugging.
|
||
|---|---|---|
| .. | ||
| keys | ||
| out | ||
| basic.conf | ||
| cleanout-gitolite | ||
| install-gitolite | ||
| README.mkd | ||
| rollback | ||
| rollback.server | ||
| t-fedora-big-config | ||
| t00-initial | ||
| t01-repo-groups | ||
| t02-user-groups | ||
| t03-branch-permissions | ||
| t03a-branch-permissions | ||
| t04-wild | ||
| t04a-wild-all | ||
| t04a-wild-students | ||
| t05-delegation | ||
| t05a-delegation | ||
| t09-oldtests | ||
| t09a-oldtests | ||
| t50-sequence-test | ||
| t51-personal-branches | ||
| t52-deny-create-ref | ||
| t53-check-info-expand-output | ||
| t59-repo-not-on-disk | ||
| test-driver.sh | ||
| update-gitolite | ||
notes on the testing setup
In this document:
- terminology
- notes and background
- quick instructions for running the test suite
- instructions for adding new tests
terminology
#define PW "patches welcome!"
#define TODO PW
notes and background
-
all testing is done on one machine, using 2 userids
-
test driver exits on the first failed test; no fancy counting here. (PW).
-
installs are done using "gl-easy-install". As such, this test suite is mainly meant for testing the core (access control) functionality, and will not help you test the install/upgrade parts themselves. Those are a lot more difficult to test in an automated fashion, but luckily they also change infrequently and can easily be tested manually when they do. Errors in those are much more visible too. (PW).
-
the test driver has evolved as new scripts were added; you will see that older scripts are a little less sophisticated.
quick instructions for running the test suite
-
create two brand new user IDs: tester and gitolite-test
- these are hard-coded, sorry. (PW)
- give them some passwords
- allow ssh into gitolite-test in
/etc/ssh/sshd_config; preferably use a line likeAllowUsers gitolite-test@127.0.0.1so that no one can ssh in from outside
-
prepare/push a bare clone of gitolite itself on /tmp so that the "tester" userid can grab it painlessly
cd your-gitolite-working-repo git clone --bare $PWD /tmp/gitolite # first time git push -f --all /tmp/gitolite # subsequent times -
"su" to "tester" and clone/fetch the gitolite source:
cd $HOME; git clone /tmp/gitolite # first time cd gitolite; git fetch origin # subsequent times -
checkout and "install" the branch you want to test (install from "tester" userid to "gitolite-test" userid). Example, if you want to test "pu" branch:
git checkout -t origin/pu # if needed git checkout -f pu; git reset --hard origin/pu # subsequent times cd t # THIS IS IMPORTANT (patches welcome, or will be fixed eventually!) ./install-gitolite -
run all or some of the tests
./test-driver.sh # or ./test-driver.sh t51
instructions for adding new tests
(TODO)