This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testsuite (was: New features of old-dejagnu.exp)
- To: oliva at dcc dot unicamp dot br, pfeifer at dbai dot tuwien dot ac dot at
- Subject: Re: Testsuite (was: New features of old-dejagnu.exp)
- From: mrs at wrs dot com (Mike Stump)
- Date: Wed, 4 Nov 1998 19:07:15 -0800
- Cc: egcs at cygnus dot com
> Date: Wed, 28 Oct 1998 15:59:35 +0100 (MET)
> From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
> One general note, though: Where is stuff like that documented?
You have read the dejagnu manual, right? Some is there.
In the testsuite. :-)/2
It was meant to be so simple as to be obvious. And for the other
stuff, asking and having the experts say sorry, can't do that... :-(
or explain how to do it.
> o the structure of the suite
> (Where to add test cases? Naming conventions?)
You can add C++ testcases anywhere under g++.old-deja. Convension,
yes, what ever you think works best on the type of tests your putting
in. My convention was to use net_n_.C, where n is previous n + 1.
That was fine until I figured out that was a stupid idea, then I
copied Jason (or was it Brendan), and went with short ids that
identify areas of the compiler. eh for exception handling, rtti for
run time tpe information, conv for conversions and so on. That is
still the one I use today.
For simplicity, I just put all my testcases in g++.mike. For others,
g++.{other,pt,eh}.
> o the features of the testsuite
> (Part of which you have described in your mail -- thanks!)
:-) I use grep and memory. If someone wants to doc it up, I'd be
happy to describe stuff.