Hey,
Thanks for the info, I haven't had a reason to use that, but now at
least I know ...
-Chris
On 3/16/06, Kazuhito SUGURI <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In article <[EMAIL PROTECTED]>,
> Wed, 15 Mar 2006 10:53:40 -0500,
> "Chris Allen" <[EMAIL PROTECTED]> wrote:
> mrchrisallen> You can always put a call to your method in setUp() . Just
> override
> mrchrisallen> that method and it is guaranteed to be called when the tests
> for this
> mrchrisallen> class begins. You can create one that looks like this and it
> should
> mrchrisallen> work fine:
> mrchrisallen>
> mrchrisallen> protected void setUp() throws Exception {
> mrchrisallen> super.setUp();
> mrchrisallen> //call your method here
> mrchrisallen> beginXXX();
> mrchrisallen> }
>
> One should not do so in the Cactus world, I think.
> setUp() and beginXXX() are having differnt role in test execution.
>
> See: http://jakarta.apache.org/cactus/how_it_works.html
> http://jakarta.apache.org/cactus/how_it_works_uml.html
>
> Regards,
> ----
> Kazuhito SUGURI
>
> ---------------------------------------------------------------------
> 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]
