Re: autotest with a direct path

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[Please keep replies on the list, so that others may chime in.  Also,
top-posting is often considered poor netiquette on mailing lists.]

According to Rikki Duncan on 5/15/2008 9:24 AM:
| First I would like to thank you for your quick responses!!  I have a
| couple more questions though.
|
| So you are saying add : address@hidden@}
| directly to my atlocal.in file, remove m4_define([baseline_files_dir],
| [/home/rikki/workspace/Ocapi/Tests]) completely and change |
| _AT_DAS_TEST([base_url/$1], [baseline_files_dir/das/$1.das]) to
| _AT_DAS_TEST([base_url/$1], [$baseline_files_dir/das/$1.das])?

Yes, that was my (untested) suggestion.

|  Then you
| are saying call ./testsuite....I am not sure where and how I do this.

Running 'autom4te --language=autotest' creates your testsuite driver,
typically named ./testsuite or tests/testsuite (depending on your choice
of AC_CONFIG_TESTDIR), which can then be used to run all or a subset of
your AT_SETUP groups.  This should be no different than from before making
these edits.

It sounds like you might like some more clarification on what autotest
does; suggestions on how to improve this chapter in the manual would be great:
http://www.gnu.org/software/autoconf/manual/html_node/Using-Autotest.html#Using-Autotest

[For starters, I think the manual should have a complete example
testsuite; particularly since
http://www.gnu.org/software/automake/manual/automake.html#Autotools-Introduction,
which has so many other examples, lacks an autotest example]

| My tests are in /home/rikki/workspace/Ocapi/Tests.  This Tests directory
| has three separate test folders(das, dds, dods) and the rest of my test
| script calls all of these tests specifically (there are 192 of them). an
| example of code is AT_DAS_RESPONSE_TEST([b31a])
| AT_DAS_RESPONSE_TEST([b31])
| AT_DAS_RESPONSE_TEST([D1])
| AT_DAS_RESPONSE_TEST([Drifters])
| AT_DAS_RESPONSE_TEST([EOSDB])

As long as AT_DAS_RESPONSE_TEST is a well-written m4 macro that expands
into an appropriate sequence of AT_SETUP/AT_CHECK/AT_CLEANUP, this seems
reasonable.  I'd recommend using a different prefix than AT_ for your own
macros, however, so that you are less likely to collide with future
autotest macros.

|
| So I guess I am asking for further clarification on exactly how to call
| the testsuite and if I am following the exact steps correctly?
|

According to Rikki Duncan on 5/15/2008 4:17 PM:
| Looking at this again, would I have to change the configure.ac file as
| well?  Now the AC_SUBST is set to AC_SUBST(host), would this stay the
| same? Do I need to add a AC_CONFIG_FILES line as well?  Were is the :
| address@hidden@} being set to my actual Tests
| directory that contains the files das, dds, dods that contain several
| baseline files?
|

configure.ac can have more than one AC_SUBST; so yes, my suggestion would
involve adding a new AC_SUBST([baseline_files_dir]), if you wanted to add
code such that configure could pick up a default value for this variable.
~  And yes, AC_CONFIG_FILES([tests/atlocal]) is necessary if you used
AC_CONFIG_TESTDIR([tests]) for autotest.  The manual also gives tips on
how to automate the creation and running of the testsuite, if you use
automake as well.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgs2bAACgkQ84KuGfSFAYBhYgCgjwj7QLHa5y3F120sb1J4G90+
krwAn3RJXoncOtEVNrk986c72AjJDL1V
=M3f5
-----END PGP SIGNATURE-----