Re: [MO-java-users] What happened to setExpectedExecuteCalls?

[Jeff M. <je...@mk...>]

Since MockStatement can now be setup with a list of return values for
executeUpdate, executeQuery and execute you don't need count the execute
calls as the lists will throw errors if you try to call executeXXX to
many or too few times.

I didn't think there was much point in deprecating it as in order to get
the tests to pass you need to setup the return lists anyways.


On Mon, 2003-04-28 at 20:08, James Howe wrote:
> I had written some tests using the 0.07 release of the library.  Recently 
> there have been some changes to the SQL related portions of the library 
> which help in writing database tests where a statement needs to return 
> multiple result sets.  I access the CVS repository and did a build to 
> create a 0.08 release.  When I tried to use it with my existing code I 
> found that much of the SQL related code had changed substantially.  For 
> example, there used to be a method on MockStatement called 
> "setExpectedExecuteCalls".  This method doesn't seem to exist any more.  
> I'm curious as to why.  Is there some other mechanism which has taken its 
> place?  Was this method considered to be not very useful?
> 
> Thanks.
-- 
Jeff Martin <je...@mk...>