[EMAIL PROTECTED] wrote:
> If the tests do not find apache httpd, they do nothing. If
> httpd is found, a private httpd server is run. htdig is run to build
> an index. htsearch is run to query the index. The results of htdig and
> htsearch are matched against expected values and the test fails if the
> results do not match.
Do we want to add individual component tests to this?
For example, someone on Digital is having problems with the htfuzzy
databases not containing useful key/data pairs.
What about code like the Transport methods and the base Connection code?
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.
-Geoff
------------------------------------
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.
