junit: Cleaning up resources

Thread view:

Maciej - 06 Oct 2006 13:22 GMT

Hi!

When I'm writing single test, it may fail() at any moment of the test.
Since I create some resources in the database in the begining of the
test, I'd like to remove them whenever the test finished (not matter
whether with success or not). Thus I'm looking for an approach like

try {
// init resources,
// test,
} finally {
// clean up resource
},

which handle with cleaning up: but for JUnit. Any idea?

Regards,

Maciej

Reply to this Message

richnjones@gmail.com - 06 Oct 2006 14:41 GMT

Try over-riding tearDown()

@Override
    protected void tearDown() throws Exception {
        super.tearDown();
        //your code here*****
    }

Richard

> Hi!
>
[quoted text clipped - 15 lines]
>
> Maciej

Reply to this Message

John - 06 Oct 2006 17:41 GMT

> Try over-riding tearDown()
>
[quoted text clipped - 25 lines]
> >
> > Maciej

In JUnit4, you can use the @After annotation.

John

Reply to this Message

Maciej - 08 Oct 2006 23:24 GMT

Thank you to all of you.

Reply to this Message

Sebastian Millies - 09 Oct 2006 09:22 GMT

Am 6 Oct 2006 09:41:33 -0700 schrieb John:

>> Try over-riding tearDown()
>>
[quoted text clipped - 9 lines]
>
> John

In DB testing it sometimes makes sense to re-use the connection over
all the tests. Unfortunately, in JUnit 4 a method to be annotated
with @AfterClass must be static, which makes it unsuitable to release
a connection in a test case instance. Why this restriction? Any way
round it?

-- Sebastian

Reply to this Message

junit: Cleaning up resources

Free Magazines