On 05/10/2011 04:56, Iain Buclaw wrote: > On 5 October 2011 00:10, Ian Lance Taylor <i...@google.com> wrote: >> Iain Buclaw <ibuc...@ubuntu.com> writes: >>
>>> First question that pops up after having a quick look is, are there >>> any tips around for writing the scripts for the testsuite? I'm not too >>> familiar with Dejagnu, and the current testsuite used for GDC D2 >>> development is written in make. >> DejaGNU is too horrible for me to talk about. I can't recommend >> anything other than blind copying of existing scripts. >> > > :-) There are at least some docs online: http://gcc.gnu.org/wiki/TestCaseWriting http://gcc.gnu.org/wiki/HowToPrepareATestcase http://gcc.gnu.org/onlinedocs/gccint/Testsuites.html#Testsuites The DejaGnu manual is available online (http://www.gnu.org/s/dejagnu/#documentation), although it's not very GCC-specific; the most useful bit is the list of command-line options (http://www.gnu.org/s/dejagnu/manual/x844.html#optiondefs) that you can pass by setting RUNTESTFLAGS="..." on the 'make check' command-line. If you're having real trouble understanding what's going on in a test script, setting RUNTESTFLAGS="-v -v -v --strace 30" will show you all the tcl commands being executed in the log file. And as Ian says, most people just copy how it's done in existing scripts. cheers, DaveK
