For people looking for an alternative take on why it is good practice to let mocked objects have default stubs for unmocked methods, see this article [1]. This article is referenced in the mocktio documentation.
[0] http://site.mockito.org/mockito/docs/current/org/mockito/Moc...
[1] https://monkeyisland.pl/2008/07/12/should-i-worry-about-the-...
I wonder if it is possible to use reflection and have mockito throw an exception if a stub method is called.
As the other reply says, that doesn't help because it never gets that far.
To my mind the article you link has the wrong premise, because I do make my data tests that way - I assert that the data is exactly what I expected. Surprise changes to data would be bad, as would surprise changes to state.