assertNotEquals about junit4

[bloritsch]

With Hamcrest, this is possible. It would look like:

assertThat( 1, not( equalTo(5) ) );

I have found that this is useful more often than you might originally think.

[trenton]

Agreed. Use assertThat instead of assertEquals and the "older" asserts supplied by JUnit directly.

[dsaff]

Looks resolved.

[dsaff]

Re-requested in http://twitter.com/#!/KevlinHenney/status/96329124712415232

[detinho]

I added assertNotEquals to Object, long and double. For which branch should I send my pull request?

[dsaff]

Marcus,

It would be against 4.10. Truth be told, I'm still not 100% sold on the functionality...

[kcooney]

If these are added, I personally think the method names should be assertNotEqual. "x equals y but y does not equal z"

In any case, could someone please provide a concrete use case where assertNotEqual(long, long) would be useful?

[dsaff]

@kcooney, I think assertNotEquals is less surprising. We already have assertNull/assertNotNull, assertSame/assertNotSame.

Hypothetically, you could imagine
long ERROR_CODE = -1;
assertNotEquals(ERROR_CODE, getResponseId());

But I'd rather have someone who recently needed the functionality chime in with their real code.

[marcphilipp]

Fixed by #418.