JUnit Test Cases @Before and @After annotations

Question

We are following below practices to write JUnit tests for our methods.

• Each method will be having their own class which holds all the tests which are required for that method. For e.g.: class test {...}

• @Before will consists of per-requisites setup for methods like "Entity" so that when we do Edit we don't need to copy/paste code for adding an entity at each method level.

Now here my question is, shall we delete all the data which we entered by writing code to trash test-data in @after method or just let it be?

I know we can make it configurable but what is best practice? keep it or delete it. As per my gut feeling deleting should be better as if there is some duplicate data already in db - it may trigger wrong true or false.

Answer 1

It depends on how much you adhere to the Don't Repeat Yourself principle. It's also worth remembering that you have @After called after each @Test and @AfterClass called after all the @Test have run. With this granularity, it should be simple to remove duplication but still split those tasks that should only run at the very end, or after each test.