search

AdrianHu99 / NOTES

0 stars 0 forks source link

https://mtlynch.io/good-developers-bad-tests/ #17

Closed AdrianHu99 closed 5 years ago

AdrianHu99 commented 5 years ago

https://mtlynch.io/good-developers-bad-tests/

AdrianHu99 commented 5 years ago

The reader should understand a test without seeing any code outside of the test function.

AdrianHu99 commented 5 years ago

Accept a degree of code redundancy if it preserves the test’s simpilicty.

AdrianHu99 commented 5 years ago

Keep helper methods free of any information the reader needs to understand the test.

AdrianHu99 commented 5 years ago

A good test name is so descriptive that a developer can diagnose failures from the name alone.