I see TestCases being generated for each of n environments (see earlier
posting of eclipse plug-in TestCase generator configured according to JNDI
name)
Then I see n TestCases being run against o Test Data Scenarios
In other words a vector where JNDI Bean1 is run against TestSuite1 (positive
test scenario TestCases case should work)
JNDI Bean1 is run against
TestSuite2..(this could be a negative test because JNDI Bean1 is not
confgured to handle TestSuite2)
JDND2 is run against
TestSuite1..(this could be a negative test because JNDI Bean2 is not
configurd tohandle TestSuite1)
Suggestions are welcome
Thanks,
Martin
----- Original Message -----
From: "J. B. Rainsberger" <[EMAIL PROTECTED]>
To: "Cactus Users List" <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 10:44 AM
Subject: Re: Automated cactus generation tool (was RE: RE: Good bye Tarek
(was RE: REPOST: RE: Authentication Failure --> Problem Found))
> Martin Gainty wrote:
>
> > Vincent,
> > I would prefer Data Driven (in an automated fashion)
> > The earlier suggestion of using an eclipse plugin interrogating xml
files
> > for JNDI names to generate Bean TestCases is of great interest to me
>
> I don't understand why you want to generate test cases. Maybe it's a
> terminology problem.
>
> Do you want to generate test case source code? or merely execute the
> same test cases on a variety of data? If it's the latter, then there are
> JUnit implementation patterns you can use for this.
> --
> J. B. Rainsberger,
> Diaspar Software Services
> http://www.diasparsoftware.com :: +1 416 791-8603
> Let's write software that people understand
>
>
> ---------------------------------------------------------------------
> 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]
