From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Regression Testing (was Re: patch #1 ...)
Date: Thu, 24 Feb 2005 17:49:00 -0000 [thread overview]
Message-ID: <20050224174136.GC24063@wookimus.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2225 bytes --]
Mel Hatzis wrote:
> If there's general interest in incorporating the test suite I have,
> I'd be happy to try and set something up.
Sounds like a great idea. Regression testing is always welcome.
> There's a perl component in it though...for setting up a test database
> against which the regression tests are run. I'm not sure how people
> feel about adding a perl dependency to the mix.
As long as the dependency is for development purposes only, I don't see
a problem. Though, committing a generated database to CVS wouldn't be
an awful idea either. ;-)
> My original idea was to have the tests run via a 'make test, but this
> was not possible since GNATS needs to be (partly) installed in order
> to run...the binaries all have a hard-wired reference to the
> 'databases' file. We could fairly easily overcome this by modifying
> the binaries to allow the databases file to be supplied...either by
> environment variable or command line option (or both).
Right. Make test could also be run after a test install directory were
created. As was mentioned in a reply to this post, it's possible to set
up the prefix to a usable test installation directory. My configure
call is usually something like this:
$ mkdir +build +install ; cd +build
$ ../configure --prefix=`pwd`/../+install \
> --with-gnats-user=$logname
$ make install
$ cd ../+install/usr/libexec/...
I do agree that enhancing command-line options would help immensely.
> The perl requirement could perhaps, be resolved, by simply committing
> the generated database to the mix.
We could always start another CVS repository for the test data and test
suite if that would be "easier". I would be fine with simply creating a
"test" directory. Is your testing suite a unit-test style?
I had been looking at GNU Nana [1]_ for design-by-contract patterns that
might be helpful. The CPP macros work best with gcc and gdb, so it's
not 100% portable to other compilers/debuggers. Might be worth looking
at, in any case.
.. [1] http://directory.fsf.org/nana.html
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
reply other threads:[~2005-02-24 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050224174136.GC24063@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).