The old method (of JUnit 3) was to mark the test-classes by extending junit.framework.TestCase. That inherited junit.framework.Assert itself and your test class gained the ability to call the assert methods this way. Since version 4 of JUnit, the framework uses Annotations for marking tests. So you no longer need to extend TestCase. But that means, … Read more
You could use the @Rule annotation with ExpectedException, like this: @Rule public ExpectedException expectedEx = ExpectedException.none(); @Test public void shouldThrowRuntimeExceptionWhenEmployeeIDisNull() throws Exception { expectedEx.expect(RuntimeException.class); expectedEx.expectMessage(“Employee ID is null”); // do something that should throw the exception… System.out.println(“=======Starting Exception process=======”); throw new NullPointerException(“Employee ID is null”); } Note that the example in the ExpectedException docs is … Read more
You’re approaching this the wrong way. Just test your functionality: if an exception is thrown the test will automatically fail. If no exception is thrown, your tests will all turn up green. I have noticed this question garners interest from time to time so I’ll expand a little. Background to unit testing When you’re unit … Read more
I think it’s quite important feature for JUnit, if author of JUnit doesn’t want the order feature, why? I’m not sure there is a clean way to do this with JUnit, to my knowledge JUnit assumes that all tests can be performed in an arbitrary order. From the FAQ: How do I use a test … Read more
The code marked @Before is executed before each test, while @BeforeClass runs once before the entire test fixture. If your test class has ten tests, @Before code will be executed ten times, but @BeforeClass will be executed only once. In general, you use @BeforeClass when multiple tests need to share the same computationally expensive setup … Read more
It depends on the JUnit version and what assert libraries you use. For JUnit5 and 4.13 see answer https://stackoverflow.com/a/2935935/2986984 If you use assertJ or google-truth, see answer https://stackoverflow.com/a/41019785/2986984 The original answer for JUnit <= 4.12 was: @Test(expected = IndexOutOfBoundsException.class) public void testIndexOutOfBoundsException() { ArrayList emptyList = new ArrayList(); Object o = emptyList.get(0); } Though answer … Read more