Mongrel users - Jul 2006 - Recommended testing approaches for new Mongrel handlers?

Okay, I got off my duff this week and have been finishing Mongrel
support for IOWA.  I now have two handlers that I need to test.  One
is similar to the Rails handler, passing request handling to IOWA
threads in the same process, and the other allows one or more Mongrel
processes to pass requests to one or more separate IOWA processes,
with session affinity.

Is there any set of standard sorts of things that have been devised to
test the other handlers that I could apply to my new handlers?


Thanks,

Kirk Haines

On Wed, 2006-07-19 at 12:00 -0600, Kirk Haines wrote:
> Okay, I got off my duff this week and have been finishing Mongrel
> support for IOWA.  I now have two handlers that I need to test.  One
> is similar to the Rails handler, passing request handling to IOWA
> threads in the same process, and the other allows one or more Mongrel
> processes to pass requests to one or more separate IOWA processes,
> with session affinity.
> 
> Is there any set of standard sorts of things that have been devised to
> test the other handlers that I could apply to my new handlers?
Kirk! You''re awake!  Awesome, since I''m actually writing the
"Mongrel
HTTP Compliance Test Suite" using RFuzz right now.  If you want I can
get with you when I have a bit to run and we can work IOWA into the
suite.

The approach of the suite is that it will start up a target web app with
a test web application in it.  Then the test suite hits it to verify it
meets compliance with the RFC.  It does this with different mongrel
configs and would run for each web framework.  The goal is to make it so
that framework authors can validate that their framework is "Mongrel
Compliant".

Hit me up in IRC if you''re game.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

On 7/19/06, Zed Shaw <zedshaw at zedshaw.com>
wrote:
> On Wed, 2006-07-19 at 12:00 -0600, Kirk Haines wrote:
>
> Kirk! You''re awake!  Awesome, since I''m actually writing
the "Mongrel
> HTTP Compliance Test Suite" using RFuzz right now.  If you want I can
> get with you when I have a bit to run and we can work IOWA into the
> suite.
That would be great.
> The approach of the suite is that it will start up a target web app with
> a test web application in it.  Then the test suite hits it to verify it
> meets compliance with the RFC.  It does this with different mongrel
> configs and would run for each web framework.  The goal is to make it so
> that framework authors can validate that their framework is "Mongrel
> Compliant".
Okay.  I have several tests in the IOWA test suite that start a simple
app for testing some aspect or other.  I''ll just roll a couple of
those for testing the Mongrel handlers with some basic tests for the
release I''m trying to get together now.  Then when you are ready, it
can undergo more extensive testing.


Thanks,

Kirk Haines

On 7/19/06, Zed Shaw <zedshaw at zedshaw.com> wrote:
> > Is there any set of standard sorts of things that have been devised to
> > test the other handlers that I could apply to my new handlers?
>
> Kirk! You''re awake!  Awesome, since I''m actually writing
the "Mongrel
> HTTP Compliance Test Suite" using RFuzz right now.  If you want I can
> get with you when I have a bit to run and we can work IOWA into the
> suite.
>
> The approach of the suite is that it will start up a target web app with
> a test web application in it.  Then the test suite hits it to verify it
> meets compliance with the RFC.  It does this with different mongrel
> configs and would run for each web framework.  The goal is to make it so
> that framework authors can validate that their framework is "Mongrel
> Compliant".
Zed, what is the state of this?  I''d love to expand on my rudimentary
tests for the IOWA+Mongrel integration and see if there''s anything
that I broke that shouldn''t be broken.


Thanks,

Kirk Haines