From: Jeremy Fincher <fincher.8@osu.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Fort?
Date: Tue, 8 Jan 2002 13:52:31 -0500 [thread overview]
Message-ID: <20020108135231.B68882@functor.resnet.ohio-state.edu> (raw)
I've been looking for a good framework to unit-test my software, and Fort seems to fit the bill. There are, however, a few things standing in my way that I'd like to resolve.
First, I *need* to link against certain C libraries, like Unix and Pcre. What do I need to do to make a fort executable that allows me to test modules linked with these libraries?
Also, are there any good examples of already-existing testing frameworks that I can base mine on? The documentation I've found isn't the most extensive, and a good example would go far to help me use it.
If I can get these issues solved, I'd be able to use Fort quite extensively for testing my software, and I'd really like to do that :)
Thanks,
Jeremy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2002-01-08 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 18:52 Jeremy Fincher [this message]
2002-01-08 19:30 ` Patrick M Doane
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=20020108135231.B68882@functor.resnet.ohio-state.edu \
--to=fincher.8@osu.edu \
--cc=caml-list@inria.fr \
/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