Geoff Hutchison writes:
> We definitely want to have an overall htdig/htsearch test (perhaps
> including queries while indexing to test reentrancy questions), but it
> seems like additional component tests would be useful as well.
Yes, that's what I'll do. Organize things so that tests are individual
when it makes sense. Something like
reset test environment
test htsearch
depends on the existence of a database, therefore run test htdig
reset test environment
test htdig
depends on nothing
There could be hints to speed up things if tests are run in sequence
reset test environment
test htdig
test htsearch
depends on the existence of a database, the database was just
built, therefore do nothing
etc.
I think I won't try to optimize this though. The test environment
must stay as simple as possible.
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
