.

1. Mockito story
from the raise of the mocking tools into
the era of continuous deployment.
by Szczepan Faber

2. TDD / XP community

3. No Getters

5. XP2000

6. “Endotesting”
“Using Mock Objects for unit testing improves
both domain code and test suites (...)”
Tim Mackinnon, Steve Freeman, Philip Craig

7. "A Brief History of Mock Objects"
"(...) many of the steps were manual, or
augmented with code generation tools. This
turned people off—they couldn't separate the
idea from the implementation"
Tim Mackinnon
mockobjects.com
JMock

8. Elsewhere, sill in 2000
by Tammo Freese

9. "EasyMock: Dynamic Mock Objects for JUnit" (2002)
“EasyMock is ideal for often-changing
interfaces inside the application, as it handles
changes to the interface quite well.”
Tammo Freese

10. "EasyMock: Dynamic Mock Objects for JUnit" (2002)
"The only drawback of EasyMock is that tests
using it are harder to read than tests using
implemented Mock Objects (...)"
Tammo Freese

11. "Mock Roles not Objects"
OOPSLA 2004

12. "Mock Roles not Objects"
“Only Mock Types You Own”
“Don’t use getters”
“Specify as little as possible in a test”
“Too Many Mocks”

13. "Mock Roles not Objects"
About EasyMock:
"(...) the simple way of defining expectations often results in
over-specified, brittle tests."

14. 2007/2008
beautiful tests
less brittleness
easy to write

15. Quality
show me your tests
and I will know all about the quality of the production code

16. Refactoring
neat and tidy tests
for poorly designed and architected production code
don’t exist

17. Timeout
If you cannot come up with a failing test in 10 minutes
take a step back and continue refactoring.

18. Pride
Test code is code.
Be proud of the code you write.

19. Recipe
+

20. Mockito popularity
9th java library or maybe 4th?

21. Problem
I’m obsessed with quality
I coached teams
I preached at conferences
I’m test driven
Every test is neat and fast
Coverage is 90%+
I release every 2 years
What’s wrong?

22. Deliver!
Quality is irrelevant
What matters is “quality delivered”

23. Mockito’s continuous deployment
every push == new version (not snapshot)
release notes and docs
automated release notes
can release from a phone
release in 10 minutes

24. To be continued…