tag:blogger.com,1999:blog-32609450.post408486451882762470..comments2023-09-15T13:14:58.827+01:00Comments on Colin Jack's Blog: BDD - Mock then replaceColin Jackhttp://www.blogger.com/profile/01403166737046938219noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-32609450.post-33946841793088041542008-03-16T21:59:00.000+00:002008-03-16T21:59:00.000+00:00Ahh yes, now that that would be interesting.I'm go...Ahh yes, now that that would be interesting.<BR/><BR/>I'm gonna give the whole mock then replace option another try manually. Maybe I'll get the advantage of the mock based design approach and end up with good acceptance tests. Maybe :)Colin Jackhttps://www.blogger.com/profile/01403166737046938219noreply@blogger.comtag:blogger.com,1999:blog-32609450.post-27798209429145141702008-03-16T16:19:00.000+00:002008-03-16T16:19:00.000+00:00Good get. I did a brief investigation into the Aut...Good get. I did a brief investigation into the AutoMockingContainer to try the "just flick a switch to go to real classes." This turned out (very quickly) to be a bad idea as you need to setup stub values to handle assertions. If a mocking framework was capable of injecting a DB when you switched to end-to-end, this might work, but It would have to be designed from the ground up.Alice Blisshttps://www.blogger.com/profile/08836600637606274136noreply@blogger.com