On Sun, Dec 20, 2009 at 12:37 AM, Krist van Besien
<[email protected]> wrote:
> On Sat, Dec 19, 2009 at 1:30 AM, Guruprasad JG <[email protected]> 
> wrote:
>> I am referring to the Apache code written in C. I would like to see if all
>> the paths are exercised for - request processing, resource management,
>> connection pooling, and configuration directives of the apache core. This
>> would be more like functional testing of apache.
>
> I think you'll have to explain to us what you exactly mean with
> checking that "all the paths are exercised". I have no clue how to
> "exercise paths" in any context, and I do consider my knowledge of the
> English language quite substantial. Maybe you should rephrase your
> question.
> If you just want to know what goes on inside Apache when a request is
> processed than you can ofcourse run it in a debugger. Will be slow,
> though. Make sure the timeout in whatever client you use is high
> enough.
>
> Krist
>
>
> --
> [email protected]
> [email protected]
> Bremgarten b. Bern, Switzerland
> --
> A: It reverses the normal flow of conversation.
> Q: What's wrong with top-posting?
> A: Top-posting.
> Q: What's the biggest scourge on plain text email discussions?
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: [email protected]
>   "   from the digest: [email protected]
> For additional commands, e-mail: [email protected]
>
>

I believe he is asking for a unit testing suite for Apache, to create
scenarios that execute every line of code in the apache webserver so
that they can verify that everything works properly, I think as a
request it's pretty ambitious...

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
   "   from the digest: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to