title: What is the best practice for checking exceptions in JUnit?
body: <p>I am trying my hand at writing test cases. From what I have read, my tests should fail from the start and I should strive to make tests pass. However, I find myself writing tests checking boundaries and the exceptions they should cause:</p>
  
  <pre><code>@Test(expected=NegativeArraySizeException.class)
  public void testWorldMapIntInt() {
      WorldMap w = new WorldMap(-1, -1);
  }
  
  @Test(expected=IndexOutOfBoundsException.class)
  public void testGetnIntnInt() {
      WorldMap w = new WorldMap(10,10);
      Object o = w.get(-1, -1);
  }
  </code></pre>
  
  <p>However, this test passes by default because Java will throw the exception anyway. Is there a better way to handle these kinds of expected exceptions, possibly a way that fails by default-- forcing me to strive to handle these cases? </p>