Confusing inconsistency in example method calls in “stubbing and verifying is redundant” note of “when” and “verify” Javadoc #3837

Currently using Mockito 5.23.0.

The Javadoc of when and of verify say:

Although it is possible to verify a stubbed invocation, usually it's just redundant. Let's say you've stubbed foo.bar(). If your code cares what foo.bar() returns then something else breaks(often before even verify() gets executed). If your code doesn't care what get(0) returns then it should not be stubbed.

I love this explanation and often want to show it to colleagues, but we then get really confused about why the example suddenly switches from foo.bar() to get(0) toward the end. This kinda defeats the purpose of me showing that stuff to others.

Maybe it’s intentional, but then I don’t get it. 🤔 It looks like a remnant from an older version of that documentation, to me (I also know that in some old versions of Mockito there used to be a suspicious link there – a colleague of mine ended up on a shady online casino website because of this 🤔 if my memories are correct).

Sidenote: There should be a space in “breaks(often” before the parenthesis.