b999d48941
We're losing the svn history (which we could probably keep if we tried hard enough) but don't consider that worthwhile. Note these tests are destructive, so run them only in a throwaway environment like a chroot, container, or vm. The tests/run.all script should be the one which launches all the tests. Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com> |
||
---|---|---|
.. | ||
chage | ||
chroot | ||
chsh | ||
cktools | ||
common | ||
convtools | ||
cptools | ||
crypt | ||
debian | ||
expiry | ||
failures | ||
grouptools | ||
log | ||
login | ||
newusers | ||
passwd | ||
split_groups | ||
su | ||
usertools | ||
bug332198-test.exp | ||
bug334803-test.exp | ||
coverage.sh | ||
README | ||
run_all |
This testsuite is NOT SECURE: it will temporarily change your passwords file with known passwords. You should run it on a chroot, or on a secured dedicated system. To test a Debian system: $ mkdir sid-chroot $ sudo debootstrap sid sid-chroot/ http://ftp.fr.debian.org/debian/ edit or copy a sources.list $ sudo cp /etc/apt/sources.list sid-chroot/etc/apt/ edit or copy a resolv.conf $ sudo cp /etc/resolv.conf sid-chroot/etc/ $ su - root -c "chroot sid-chroot/ /bin/bash" # mount -t proc proc /proc # mount -t devpts devpts /dev/pts # aptitude update # aptitude install expect # cd /dev ; mknod --mode=666 /dev/ptmx c 5 2