Re: [Webwork-devel] StrutsTestCase for JUnit

[Mike Cannon-B. <mi...@at...>]

I might just mention that this of course depends on what your WebWork
actions do / talk to ;)

(ie if your webwork action creates an EJB - you still need to run it in a
container to test effectively)

This is probably obvious but it doesn't hurt to have it in the archives ;)

This is a very cool feature of WW even so.

-mike

Mike Cannon-Brookes
mi...@at...

ATLASSIAN - Your J2EE Expert Partner
--------------------------------------------------------
> Brilliant Software - http://www.atlassian.com/software
> Legendary Services - http://www.atlassian.com/support

On 19/2/02 12:14 AM, "Maurice Parker" (Ma...@Vi...)
penned the words:

> 
> On Sunday, February 17, 2002, at 07:42  PM, Edwin Desouza wrote:
> 
>> Rickard,
>> Maybe a clone of this for WebWork....
>> 
>> http://strutstestcase.sourceforge.net/
> 
> The need to use Cactus, StrutsTestCase, etc.. when testing Struts is due
> to the fact that Struts actions are contaminated by HttpServletRequest and
> HttpServletResponse.  This contamination makes Struts actions difficult to
> use outside of a servlet container.  You always have to do mock objects or
> have the container present.
> 
> This is totally unnecessary for WebWork.  :-)  Because of the
> exceptionally clean separation of Presentation vs. Business logic in
> WebWork you don't need an extra project to use it in an automated testing
> environment (or any other environment).  JUnit is the only thing you need
> to write fully automated tests for WebWork actions.
> 
> -Maurice
> 
> 
> _______________________________________________
> Webwork-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-devel