From 770794f1d24a6bfb4eacabcc8f272e4bb44890ab Mon Sep 17 00:00:00 2001 From: hunt Date: Wed, 19 Sep 2007 16:35:02 +0000 Subject: 2007-09-19 Martin Hunt PR 4931 * test-debug.tcl (cleanup): Remove print. * README: Update. * syscall.exp: Source test.tcl and call run_one_test() from there. * test.tcl: Rewrite as a function. Do compilation as well as testing. Compile into and execute in a directory in /tmp. --- testsuite/systemtap.syscall/README | 27 +++------------------------ 1 file changed, 3 insertions(+), 24 deletions(-) (limited to 'testsuite/systemtap.syscall/README') diff --git a/testsuite/systemtap.syscall/README b/testsuite/systemtap.syscall/README index 41e6d895..480bd8cd 100644 --- a/testsuite/systemtap.syscall/README +++ b/testsuite/systemtap.syscall/README @@ -1,32 +1,11 @@ How these tests work: Dejagnu finds all *.c files, compiles them and runs them in a temporary -directory while running the systemtap script sys.stp. To avoid -recompiling sys.stp over and over, the test.exp is smart enough to -compile sys.stp once and save the module. +directory while running the systemtap script sys.stp. - -You can run all the tests here with -> runtest test.exp - -You can run single tests with +If you need to know why a test is failing you can look in the test log, or > gcc -o testname testname.c ->./test.tcl testname - -OR, if you want to run multiple tests and don't want all the delays -with recompiling sys.stp each time, - -> stap -kp4 sys.stp -Keeping temporary directory "/tmp/stapPThTaQ" -> ./test.tcl testname /tmp/stapPThTaQ/*.ko -> ./test.tcl testname2 /tmp/stapPThTaQ/*.ko -... -> rm -rf /tmp/stapPThTaQ - -Finally, if you need to know why a test is failing, use -"test-debug.tcl" exactly as above. After running the test, it will open a -window with the results and expected results. - +> test-debug.tcl testname HOW TO WRITE TESTS -- cgit