This test should fail, as the interface specifies that the result is the
same.
See the TestAbstractOrderedBidiMapDecorator class (of yours ;-) I just
checked in amended. Note the special handling for inverse.
Stephen
- Original Message -
From: Michael Heuer [EMAIL PROTECTED]
In a situation where I have an unit test that extends AbstractTestBidiMap
for a class that extends AbstractBidiMapDecorator,
Testcase: testBidiInverse took 0.01 sec
FAILED
Inverse of inverse is not equal to original. expected same:{key1=value1,
key3=value3, key2=value2} was not:{key1=value1, key3=value3,
key2=value2}
junit.framework.AssertionFailedError: Inverse of inverse is not equal to
original. expected same:{key1=value1, key3=value3, key2=value2} was
not:{key1=value1, key3=value3, key2=value2}
...
This seems a bit odd, assertSame seems to not do the right thing here.
michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
