[1781] in Kerberos_V5_Development
kadm5 unit tests ported
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Tue Sep 24 16:03:29 1996
Date: Tue, 24 Sep 1996 16:03:20 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: krbdev@MIT.EDU
I have made a first pass at making OV's kadm5 tests work with the
current build system. I am not finished, but it is far enough along
that other people could bang on it on other platforms. Various
details:
1. Tests exist in lib/kadm5, kadmin/passwd, and kadmin/v4server, each
in the "unit-test" subdirectory. Run cvs update in lib/kadm5 and
kadmin.
2. In each unit-test directory, the target unit-test runs the entire
test (I also created the target check as a duplicate). Generally,
unit-test has three sub-targets, unit-test-setup, unit-test-body, and
unit-test-cleanup, that it runs in that order. unit-test-setup
creates a new database in a known state and starts the kdc and
kadmind; unit-test-cleanup kills the servers but leaves the database
around in case you want to play with it. The lib/kadm5 and
kadmin/passwd tests can be run as any user, but kadmin/v4server tests
must be run as root (because it uses port 750).
3. The tests assume that /krb5 is writeable by the user running the
tests. Everything in /krb5 will be destroyed by unit-test-setup;
obviously, this should be fixed to allow a specifiably directory to be
used.
4. You will need to create symlinks from build/kadmin/testing/scripts
to the source tree, because the tests run some scripts from
$(BUILDTOP) directories explicitly. I haven't decided on the right
way to fix this yet.
5. The tests use dejagnu (except for a few additional test programs
in lib/kadm5/unit-test that are run directly by the makefile).
runtest is always given the --debug flag, and dbg.log is your friend
(albeit a hard friend to understand sometimes :-).
6. Good luck, you'll need it.
Barry
