[Junit-devel] reintroduction of assertion variants for primitive types?

[Yanic I. <yan...@te...>]

Hi all,

re: org.junit.Assert.java      (rev 1.1.2.7, "Version4" branch, 
"NewYears2006" tag)

In this commit (by kbeck) the decision was made to remove all 
'superfluous' assertEquals variants for primitive types from 
org.junit.Assert and rely on auto-boxing and the Object-based variant 
instead.

Have you taken into consideration that some programmers are not that 
keen (yet?) on auto-boxing and have their compiler set to report 
warnings/errors when auto-boxing is detected?

To circumvent such warnings/errors in their testcode, these programmers 
have to forsake assertEquals and use assertTrue (which is not as 
legible, neither in testcode nor in testrunner output). IMHO the 
framework shouldn't force the use of auto-boxing on its users. 
Auto-boxing can easily be avoided by providing variants for each 
primitive type (as it was before), at no cost and without breaking 
existing code.

Any chance on a reintroduction of these assertEquals (and related) 
variants for primitive types?

Best regards,
Yanic