Closed AdrianHu99 closed 5 years ago
The reader should understand a test without seeing any code outside of the test function.
Accept a degree of code redundancy if it preserves the test’s simpilicty.
Keep helper methods free of any information the reader needs to understand the test.
A good test name is so descriptive that a developer can diagnose failures from the name alone.
https://mtlynch.io/good-developers-bad-tests/