Mailing-List: contact turbine-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Turbine Users List" <turbine-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Tue, 7 Nov 2006 09:21:56 -0500 (EST)
From: Jeffery Painter <painter@kiasoft.com>
To: turbine-user@jakarta.apache.org
Subject: turbine 2.3.1 and Unit Testing
Message-ID: <Pine.LNX.4.63.0611070918350.1444@kiasoft.user.openhosting.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


Hello again,

I am trying to create unit tests for my application and trying to figure 
out what is the current "best practice"... I have looked at EasyMock, 
Cactus and Mockobjects... some of these seem old and others more 
complicated to get setup.

There also seems to be some lacking help in the area of setting up your 
build environment with the proper testing jar's in order to get Eclipse to 
run the unit tests properly..

do you test against a database or do you just test functionality of action 
and om classes?

If you have a good working test case for an action class (and can tell me 
how you setup your Eclipse environment build path) this would be of great 
help.

Thanks for listening...

Jeffery Painter
----------------------------------------------------------
     324 Birdsong Way
     Holly Springs, NC 27540-8989       voice: 919.321.0378
     painter@kiasoft.com     http://www4.ncsu.edu/~jlpaint2
----------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org