Well after two days of figuring out I have some sort of working setup. It still uses way too much shell code IMO, but at least it works. If I find the time I might try to do a write-up of how to write tests in dejagnu because I found it hard to do.

In the rdup source you can now do a make check which should like this:

[ -d testlogs ] || mkdir testlogs
chmod +x testsuite/rdup/rdup*helper
runtest 
Test Run By miekg on Mon May  4 20:38:23 2009
Native configuration is i686-pc-linux-gnu

        === rdup tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
WARNING: Couldn't find tool config file for unix, using default.
Running ./testsuite/rdup/rdup.full.exp ...
Running ./testsuite/rdup/rdup.incr.exp ...
Running ./testsuite/rdup/rdup.ln-up.exp ...
Running ./testsuite/rdup/rdup.ln.exp ...
Running ./testsuite/rdup/rdup.m-flag.exp ...
Running ./testsuite/rdup/rdup.mvdir.exp ...
Running ./testsuite/rdup/rdup.newdir.exp ...
Running ./testsuite/rdup/rdup.nonzero.exp ...
Running ./testsuite/rdup/rdup.pipeline.exp ...
Running ./testsuite/rdup/rdup.r-flag.exp ...
Running ./testsuite/rdup/rdup.rdup-up.exp ...
Running ./testsuite/rdup/rdup.run-tr.exp ...
Running ./testsuite/rdup/rdup.run-up.exp ...
Running ./testsuite/rdup/rdup.run.exp ...

        === rdup Summary ===

# of expected passes        14

14 tests which are all passed :) For details I refer to the source.