On 21/04/2010, Mike Dillon <m...@embody.org> wrote: > Shouldn't that be assertSame() to retain the meaning of "=="?
In this case, the operands were primitives (int/long) which are not supported by assertSame(). But agreed - assertSame() would be needed for object comparisons. > -md > > > "sebb" <seb...@gmail.com> wrote: > > >I just changed TestIdentityInputStream to use assertEquals(exp,actual) > >rather than assertTrue(actual==exp), as this shows the actual and > >expected values if the test fails. > > > >Any objections if I work through the other test classes doing the same? > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > >For additional commands, e-mail: dev-h...@hc.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
