What is a better practice?

[Alexander Sales]

One assert per test?

or

the other way around...

like for example :

@Test
public void resultShouldBeZero(){
   assertEquals(0,new Code.getResult());
}
@Test
public void resultShouldBeOver100(){
   assertEquals(115,new Code.getResult());
}
@Test
public void resultShouldBeLess100(){
   assertEquals(99,new Code.getResult());
}

or

@Test
public void testResult(){
   assertEquals(0,new Code.getResult());
   assertEquals(99,new Code.getResult());
   assertEquals(115,new Code.getResult());
}

[Jeanne Boyarsky]

Alexander,
The idea of one assertion per test is to be testing one thing in each test. That may require one assertion. In your example, each of the three assertions is independent and makes sense to be in a separate test. The clue is that you have clear "business" types names for each test.

Consider this example:

@Test
public void coordinatesFound() {
  Coordinates actual = realCode...
  assertEquals("x", 1, actual.getX());
  assertEquals("y", 2, actual.getX());
}

I'm testing one business case/scenario although I happen to use two assertions. I might even refactor the assertions to another method to show they go together.

@Test
public void coordinatesFound() {
  Coordinates actual = realCode...
  assertCoordinates(1, 2actual);
}

[Alexander Sales]

yes, that's a good approach. Thanks Jeanne.