You may well be right. Anyone think the opposite?
b.t.w. I'd love to hear more about your experiences.
In the meantime, you might also want to take a look at the new dynamic
mock stuff in the library.
S.
ric...@vo... wrote:
> Hi all,
>
> We're using mockobjects heavily for our unit tests.
>
> Currently we're testing a sql-update with PreparedStatement.
>
> I noticed that CommonMockPreparedStatement is using ExpectationSet, which is
> using HashSet for internal storage. Since HashSet doesn't have a guaranteed
> iteration order, it is in my opinion not suitable for PreparedStatement.
> CommonMockPreparedStatement should use ExpectationList instead, so the order
> is guaranteed (which is very important in a PreparedStatement...)
>
> Richard.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Mockobjects-java-users mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-users
|
