In my view of testing software you have two different categories:

 * unit testing - almost no dependencies, like no containers
 * module testing - testing components in the production environment, or 
   at least something close to it

I used MockEJB to test things like a complex class that for some reason 
had dependencies on the container interfaces: JNDI and JMS. It was very good 
for this and I was capable of asserting that my class was sending the expected 
messages.

This was totally outside of the container, so, it is very fast, no need to have 
an AppServer, DBMS, etc. More important, my possible points of failure in these 
tests were my class, my test and of course MockEJB ;-)

Best regards / Beste Grüße / Cumprimentos,

Luis Sergio Oliveira


-----Original Message-----
From: Rod Macpherson [mailto:[EMAIL PROTECTED] 
Sent: terça-feira, 4 de Outubro de 2005 8:12
To: Cactus Users List; bala chandar
Subject: RE: EJB Persistance Testing


Question: why bother when you can test them for real? 

-----Original Message-----
From: bala chandar [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 03, 2005 9:51 PM
To: Cactus Users List
Subject: Re: EJB Persistance Testing

hi martin,
 You can go for MockEJB to test CMP.
 It is purely outcontainer testing. You can use Junit with MockEJB to
check the assertions.
 U can check it on www.mockejb.org <http://www.mockejb.org>  Regards
bala

 On 10/4/05, Martin Ying <[EMAIL PROTECTED]> wrote:
>
> Newly test infected, however don't see how to create CMP and BMP test.

> My lack of testing experience is raising questions like what should I 
> be testing, how do I design good test for EJB persistence. It's either

> in the DB or not, what's there to test? Are there good article and/or 
> books that go into detail about designing test cases specifically for 
> EJB persistence layer testing? Thanks!
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to