Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 67299 invoked by uid 500); 5 Jul 2001 01:38:33 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 67288 invoked from network); 5 Jul 2001 01:38:32 -0000 Date: Wed, 4 Jul 2001 18:38:03 -0700 (PDT) From: X-Sender: To: Subject: Re: test harness for Apache In-Reply-To: <3B43C4DE.9080300@cnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Wed, 4 Jul 2001, Ian Holsman wrote: > Chuck Murcko wrote: > > > I believe Ian Holsman has been working on this for a bit already. > > I have a test harness for the pools code, which reads in a file, spawns > multiple threads and does the corresponding > pool function calls in each thread. The APR functions already have a test harness. The harness Phil is talking about will test Apache itself. > It could easily be adapted to check status codes and compare them with what > the program actually returned.. > > I also am going to do one for the buckets so you can replay bucket > functions. Cool. Ryan _____________________________________________________________________________ Ryan Bloom rbb@apache.org Covalent Technologies rbb@covalent.net -----------------------------------------------------------------------------