In my opinion, asking this question is the key benefit of test-driven development. You get to be the consumer, write down your expectations, and then work backwards from yours-as-consumer expectations.

I find the opposite tends to happen in Java. In the pursuit of testability, people make libraries much harder to use and understand.

Writing good tests is a skill that has to be developed, just like anything else.

It should be, but too often people write bad tests that test whst they wrote and not what it’s supposed to do.

Writing good tests is a skill and most developers don’t seem to be as skilled in it as they think.

The same concepts power much of Agile too though: XP & Scrum both complement this.