You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Warner Onstine <wa...@warneronstine.com> on 2001/12/22 04:11:01 UTC
Cactus testing with a framework such as Turbine
Hi all,
I have been searching for good documentation or examples regarding testing a
Turbine/Velocity application with Cactus. I just bought the wonderful book
Java tools for extreme programming (thanks Nick!), but I am still struggling
with what needs to be done in order to test my classes.
For those not familiar with Turbine here is a simple setup:
1. Turbine is the servlet that all requests go through.
2. It uses an properties file to start up its various services (which as an
app framework it relies on) such as Velocity, Intake, PoolService (database
is what I rely on here)
3. Whenever a doGet or doPost is performed it either creates or looks for a
RunData instance
4. This instance of RunData gets passed to various classes which I want to
test as well as a Context (this is defined in my case by the Velocity
service)
5. A lot of things are passed into the context that I need access to such as
the Intake service instance.
So, given all of this what is my best approach? I don't want to test Turbine
I just want to test my application in relation to Turbine (granted if there
are problems with the framework I will be testing Turbine =).
I did search the archives for this, but didn't find anything in user (did
find mention of turbine in v2 mail about a month ago). Do I need to wait for
v2 (need help on the Turbine part?).
-warner
+warner onstine+
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Cactus testing with a framework such as Turbine
Posted by Warner Onstine <wa...@warneronstine.com>.
----- Original Message -----
From: "Vincent Massol" <vm...@octo.com>
To: "'Cactus Users List'" <ca...@jakarta.apache.org>
Sent: Saturday, December 22, 2001 12:56 AM
Subject: RE: Cactus testing with a framework such as Turbine
> Hi Warner,
>
> I have never used Turbine so I probably won't be of good help ... I can
> explain the principle but I don't know if it is easy to apply or not.
> The idea is that you look at the method you want to test and find out
> what you need to initialize beforehand. The format is :
>
> <inits>
>
> MyClassToTest object = new MyClassToTest();
> Object.methodToTest(...);
>
> <asserts>
>
> Thus, if in methodToTest() you need a Context object, you'll need to
> create one in the <inits> section. Cactus will be able to provide the
> standard Servlet API objects to your code (HttpServletRequest, ...) so
> you don't have to create these, you can use them directly. However,
> Cactus does not provide any Turbine or Velocity objects so you'll need
> to find a way to create them yourself.
>
> Basically there are 2 strategies :
> - create mock implementations of them,
> - instantiate real objects
>
> The idea of Cactus is to provide integration unit test, so it is better
> if you succeed in instantiating the real objects. If you go on the mock
> objects route (www.mockobjects.com), you'll have to decide whether you
> still want to use Cactus or simply use JUnit and use the mock servlet
> api implementation from www.mockobjects.com for example.
Unfortunately I think that there is too much configuration (or too many mock
objects to create for testing Turbine) for me to try the mock objects route
right now. One of the reasons I was looking at Cactus.
> Hope it helps a bit.
> -Vincent
>
> P.S. : You can have a look at the StrutsTestCase project which lets you
> unit test Struts actions on top of Cactus. URL =
> http://strutstestcase.sourceforge.net/
Thanks this is very helpful! Anyone know of a similar project for Turbine
(hope, hope!).
-warner
> > -----Original Message-----
> > From: Warner Onstine [mailto:warner@warneronstine.com]
> > Sent: 22 December 2001 04:11
> > To: cactus-user@jakarta.apache.org
> > Subject: Cactus testing with a framework such as Turbine
> >
> > Hi all,
> > I have been searching for good documentation or examples regarding
> testing
> > a
> > Turbine/Velocity application with Cactus. I just bought the wonderful
> book
> > Java tools for extreme programming (thanks Nick!), but I am still
> > struggling
> > with what needs to be done in order to test my classes.
> >
> > For those not familiar with Turbine here is a simple setup:
> > 1. Turbine is the servlet that all requests go through.
> > 2. It uses an properties file to start up its various services (which
> as
> > an
> > app framework it relies on) such as Velocity, Intake, PoolService
> > (database
> > is what I rely on here)
> > 3. Whenever a doGet or doPost is performed it either creates or looks
> for
> > a
> > RunData instance
> > 4. This instance of RunData gets passed to various classes which I
> want to
> > test as well as a Context (this is defined in my case by the Velocity
> > service)
> > 5. A lot of things are passed into the context that I need access to
> such
> > as
> > the Intake service instance.
> >
> > So, given all of this what is my best approach? I don't want to test
> > Turbine
> > I just want to test my application in relation to Turbine (granted if
> > there
> > are problems with the framework I will be testing Turbine =).
> >
> > I did search the archives for this, but didn't find anything in user
> (did
> > find mention of turbine in v2 mail about a month ago). Do I need to
> wait
> > for
> > v2 (need help on the Turbine part?).
> >
> > -warner
> >
> > +warner onstine+
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:cactus-user-
> > unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:cactus-user-
> > help@jakarta.apache.org>
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Cactus testing with a framework such as Turbine
Posted by Vincent Massol <vm...@octo.com>.
Hi Warner,
I have never used Turbine so I probably won't be of good help ... I can
explain the principle but I don't know if it is easy to apply or not.
The idea is that you look at the method you want to test and find out
what you need to initialize beforehand. The format is :
<inits>
MyClassToTest object = new MyClassToTest();
Object.methodToTest(...);
<asserts>
Thus, if in methodToTest() you need a Context object, you'll need to
create one in the <inits> section. Cactus will be able to provide the
standard Servlet API objects to your code (HttpServletRequest, ...) so
you don't have to create these, you can use them directly. However,
Cactus does not provide any Turbine or Velocity objects so you'll need
to find a way to create them yourself.
Basically there are 2 strategies :
- create mock implementations of them,
- instantiate real objects
The idea of Cactus is to provide integration unit test, so it is better
if you succeed in instantiating the real objects. If you go on the mock
objects route (www.mockobjects.com), you'll have to decide whether you
still want to use Cactus or simply use JUnit and use the mock servlet
api implementation from www.mockobjects.com for example.
Hope it helps a bit.
-Vincent
P.S. : You can have a look at the StrutsTestCase project which lets you
unit test Struts actions on top of Cactus. URL =
http://strutstestcase.sourceforge.net/
> -----Original Message-----
> From: Warner Onstine [mailto:warner@warneronstine.com]
> Sent: 22 December 2001 04:11
> To: cactus-user@jakarta.apache.org
> Subject: Cactus testing with a framework such as Turbine
>
> Hi all,
> I have been searching for good documentation or examples regarding
testing
> a
> Turbine/Velocity application with Cactus. I just bought the wonderful
book
> Java tools for extreme programming (thanks Nick!), but I am still
> struggling
> with what needs to be done in order to test my classes.
>
> For those not familiar with Turbine here is a simple setup:
> 1. Turbine is the servlet that all requests go through.
> 2. It uses an properties file to start up its various services (which
as
> an
> app framework it relies on) such as Velocity, Intake, PoolService
> (database
> is what I rely on here)
> 3. Whenever a doGet or doPost is performed it either creates or looks
for
> a
> RunData instance
> 4. This instance of RunData gets passed to various classes which I
want to
> test as well as a Context (this is defined in my case by the Velocity
> service)
> 5. A lot of things are passed into the context that I need access to
such
> as
> the Intake service instance.
>
> So, given all of this what is my best approach? I don't want to test
> Turbine
> I just want to test my application in relation to Turbine (granted if
> there
> are problems with the framework I will be testing Turbine =).
>
> I did search the archives for this, but didn't find anything in user
(did
> find mention of turbine in v2 mail about a month ago). Do I need to
wait
> for
> v2 (need help on the Turbine part?).
>
> -warner
>
> +warner onstine+
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>