Sure, they have to be static. It's a slight mistake I've made, thanks for pointing that out Enrique and to have conformed it Chris !
On 10/5/07, Chris Custine <[EMAIL PROTECTED]> wrote: > Yes indeed, those methods should be static. > > Chris > > > On 10/5/07, Enrique Rodriguez <[EMAIL PROTECTED]> wrote: > > Hi, Directory developers, > > > > I tried out Emm's JUnit4 primer. It looks like the per-class methods > > need to be static. If others verify this, I can update the primer. > > Correct method signatures: > > > > @BeforeClass > > public static void globalSetUp() > > > > @AfterClass > > public static void globalTearDown() > > > > This is in the "giant leap for testers" section. > > > > Primer: > > > > > http://cwiki.apache.org/confluence/display/DIRxDEV/JUnit4+primer > > > > Enrique > > > > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
