http://www.thedwick.com/blog/2010/01/resultset-mocking-with-jmock/ Technologists Who Speak Business Thu, 09 Dec 2010 20:40:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.thedwick.com/blog/2010/01/resultset-mocking-with-jmock/comment-page-1/#comment-19271 Tim Cull Sat, 23 Jan 2010 15:59:08 +0000 http://www.thedwick.com/blog/?p=239#comment-19271 Mmm I have never used States before but I like what you've done with them very much Mmm I have never used States before but I like what you’ve done with them very much

]]> http://www.thedwick.com/blog/2010/01/resultset-mocking-with-jmock/comment-page-1/#comment-19269 Steve Freeman Sat, 23 Jan 2010 15:01:39 +0000 http://www.thedwick.com/blog/?p=239#comment-19269 Looking again, you might be better off with more of a builder style to construct an expectations. I've posted an example at http://pastie.org/791222 Looking again, you might be better off with more of a builder style to construct an expectations. I’ve posted an example at http://pastie.org/791222

]]> http://www.thedwick.com/blog/2010/01/resultset-mocking-with-jmock/comment-page-1/#comment-19268 Steve Freeman Sat, 23 Jan 2010 10:57:56 +0000 http://www.thedwick.com/blog/?p=239#comment-19268 Interesting solution to a tricky problem. I think some of the constraints could be relaxed. For example, clauses like one(rs).getInt(column) could use the allowing() clause since they're effectively queries. On the other hand, you might also want to use States to enforce that the close calls are made last. Interesting solution to a tricky problem. I think some of the constraints could be relaxed. For example, clauses like one(rs).getInt(column) could use the allowing() clause since they’re effectively queries. On the other hand, you might also want to use States to enforce that the close calls are made last.

]]>