This text was originally posted at Pragmatists blog
In automated testing it is common to use objects that look and behave like their production eq...
For further actions, you may consider blocking this person and/or reporting abuse
I love the graphics. Really well-explained, Michal.
Perfect. Very clean explanation.
I would just add that regarding this part of the code:
when(gradebook.gradesFor(student)).thenReturn(grades(8, 6, 10));
The first part:
when(gradebook.gradesFor(student)) is also a mock. Because if the method gradesFor is called with another parameter, will never return what we expected.
You are not explicit doing a mock as when using "verify", but is still mock.
Love this article! Nice way of defining theses concepts.
Definitely an easy to follow article to refer to when people are talking about the topic and misusing the terms. And the graphics are awesome
Short and clear. Thanks.
Nice article. Where did you create the diagrams? They're cool.