Re: Generating Test Suites with Autotest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Sat, Jun 11, 2005 at 10:02:27AM +0200, Ralf Wildenhues wrote:
> * Gander wrote on Fri, Jun 10, 2005 at 09:55:53PM CEST:
> > I have a had a stab at building tests into configure.ac/Makefile.am
> > etc. from section 16 of the manual but don't find it easy to follow.
...
> > Has anyone got any other simpler notes?
> 
> Not really.  A combination of looking at Autoconf's testsuite itself,
> the autotest/general.m4 file, and the info docs you mentioned, have
> helped me get going for the new Libtool testsuite (which can be found
> in its CVS HEAD).

actually, there is a connected question: why should one use Autotest
for automated testing?

Even though I like m4 and Autoconf internals, Autotest still scares me.
The simple *.test files used by Automake test suite seems to be much
simpler.

What are the advantages of Autotest?  Perhaps the Automake system is more
relaxed?  Does it compare stdout and stderr with the expected one?

If someone knowledgable could produce a quick comparison, I'd be interested.
(Noah? or someone from the team publishing under the name of Alexandre? ;-)

And then there is dejagnu: what's its role here?

Thanks in advance for any pointers,
	Stepan


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux