On Thu, Mar 3, 2011 at 11:50 PM, Moandji Ezana <[email protected]> wrote:
> On Thu, Mar 3, 2011 at 12:16 PM, Miroslav Pokorny < > [email protected]> wrote: > >> Heres a crazy question, does the need for a mocking framework imply that >> perhaps theres something wrong w/ your design ? Why cant you simply create >> the necessary interface and assert the inputs and return some output ? > > > "creating the necessary interface and asserting the inputs and returning > some output" *is* mocking and you can perfectly well do it by hand. In some > edge cases, it's actually easier to not use a library. The libraries just > make the usual case easier and less verbose. > > Having to mock a lot might well mean that there's something wrong with the > design, the test or both. > > Moandji > > My statements were directed towards using a mocking framework which implies you have a complex problem so need something a bit more complex than just creating some dumb interface impl, > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- mP -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
