Re: [MO-java-users] CommonMockPreparedStatement is using ExpectationSet:no guaranteed iteration order

[Olaf K. <ok...@ab...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Martin wrote:
| I can't see quite what the issue is. Which ExpectationSet are we
talking
| about? The expected parameters are being stored as key value pairs so
|
| setObject(1,"Stuff");
| setObject(2,"More Stuff");
|
| is the same as
|
| setObject(2,"More Stuff") ;
| setObject(1,"Stuff");

what about:

addExpectedSetParameter(1, "firstpass")
addExpectedSetParameter(2, "firstpass")
addExpectedSetParameter(1, "secondpass")
addExpectedSetParameter(2, "secondpass")
setExpectedExecuteCalls(2)
...

this is also passed by

setParameter(1,"secondpass");
setParameter(2,"firstpass");
execute();
setParameter(1,"firstpass");
setParameter(2,"secondpass");
execute();

I personally can *well* live with this, as it allows to split
expectations between setUp and test without much hassle.
In my eyes there's no need to change (would probably break my tests :-)

Best,

Olaf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+X2Nc7/xtFKqdCzURAgGZAJ0f3zXH2E3RXuLTFgIemuvNk0cUsQCgmfkK
3s+PobDWf/kYS2yLsIuyjl4=
=eDCv
-----END PGP SIGNATURE-----