When I am running TDD workshops we talk about a what a readable test is.

I mean one that easily expresses the contract of the code under test.

I want to see the “API”.

If you use a library that hides that API from me, focusing instead on the GWT etc, that’s not readable

That’s not to say that I don’t think the Act/Arrange/Assert approach is not valuable in structuring the test. I do.

But how you express AAA or GWT is not the focus- the contract that I diacivwres through TDD is and the tests should be examples of how to use it.

diacivwres is discover