Ole,
Hi!
>
> I was thinking about using the
> CtsBmpBean as a resource for testing.
> However, this has some private methods
> setUp() and tearDown() for initializing
> the database. Before every create these
> two methods are created, so I guess it
> is impossible to create two instances
> here.
> Would anybody object if I changed this
> to a initDB() home method that ensures
> an empty table is present?
>
My motivation for those private methods was simply to
first ensure that the table existed at the onset of
the test and second that the DB schema was as it
began... empty. A non-invasive test if you will with
everything being left as it was.
So... if this philosphy is followed, I wouldn't think
that any harm would be done to the CTS tests...
cheers,
peter
P.S. BTW, I'm going to be checking in a bit more BMP
stuff tonight. In particular I coded some JMS
callbacks that verify container callbacks on the bean
instance were called. Also I coded a CMP also...
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
