jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Appling" <steve...@appling.org>
Subject Re: Multi Step Tests - Better HttpUnit Integration
Date Thu, 26 Sep 2002 16:07:18 GMT
What Cactus buys me is the ability to have a test running in the container
with an instance of my servlet.  After all of the setup (which is what I am
using HttpUnit for) I can make asserts about the internal state of my
Servlet.  I don't have a way of doing this by just looking at the servlet's
response with HttpUnit.

It may be possible to preset the state of my system before this one call,
but it would be extremely complicated.  The particular servlets under test
rely on other parts of the web application being set up.  Some of those
parts are outside of my control and do not have a convenient mechanism to
initialize them to a particular state.  It seems that the most reliable way
of running my test in the actual context that the code will execute under
when in production is to actually generate the required pre-requisite

----- Original Message -----
From: "Larry Tambascio" <ltambascio@charter.net>
To: "Cactus Users List" <cactus-user@jakarta.apache.org>
Sent: Thursday, September 26, 2002 11:48 AM
Subject: Re: Multi Step Tests - Better HttpUnit Integration

> Hi Steve,
> It sounds to me like what you really need is HttpUnit.
>  I'm unsure what Cactus is buying you.  What I have
> usually done is to setup the session as though all your
> preceding requests and responses have been made.  My guess
> is that it would take about the same amount of code to
> setup all the session values as it does to do the HttpUnit
> web conversation thing.  Finding out what those all are
> could be tedious, but it would make your tests cleaner and
> faster, IMHO.
> -Larry

To unsubscribe, e-mail:   <mailto:cactus-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:cactus-user-help@jakarta.apache.org>

View raw message