Return to Answer

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

It's probably the easiest solution for your problem, but from the viewpoint of good design practice this should be avoided.

edit:

There are annotations in jUnit: Different teardown for each @Test in jUnit

edit2:

The setUp() method is invoked before every test. You use it to initialize variables and clean up from previous tests. You can also use the JUnit tearDown() method, which runs after every test method. The tutorial does not use it.

http://developer.android.com/tools/testing/activity_test.html

If you have different tearDown() Methods for each test, I think you need to change them.

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

It's probably the easiest solution for your problem, but from the viewpoint of good design practice this should be avoided.

edit:

There are annotations in jUnit: Different teardown for each @Test in jUnit

edit2:

The setUp() method is invoked before every test. You use it to initialize variables and clean up from previous tests. You can also use the JUnit tearDown() method, which runs after every test method. The tutorial does not use it.

http://developer.android.com/tools/testing/activity_test.html

If you have different tearDown() Methods for each test, I think you need to change them.

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

It's probably the easiest solution for your problem, but from the viewpoint of good design practice this should be avoided.

edit:

There are annotations in jUnit: Different teardown for each @Test in jUnit

what are you using on android?

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

It's probably the easiest solution for your problem, but from the viewpoint of good design practice this should be avoided.

edit:

There are annotations in jUnit: Different teardown for each @Test in jUnit

edit2:

The setUp() method is invoked before every test. You use it to initialize variables and clean up from previous tests. You can also use the JUnit tearDown() method, which runs after every test method. The tutorial does not use it.

http://developer.android.com/tools/testing/activity_test.html

If you have different tearDown() Methods for each test, I think you need to change them.

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

Test like this:

try{ setUp(); /* do some testing*/ }catch(Exception ex){ /* do something with the exception */ /* let the test fail */ }finally{ tearDown(); } 

It's probably the easiest solution for your problem, but from the viewpoint of good design practice this should be avoided.

edit:

There are annotations in jUnit: Different teardown for each @Test in jUnit

what are you using on android?