“
Tests shouldn’t verify units of code. Instead they should verify units of behavior: something that is meaningful for the problem domain and ideally something that a business person can recognize as useful. The number of classes it takes to implement such a unit of behavior is irrelevant. The unit could span across multiple classes or only one class, or even take up just a tiny method. [...] A test should tell a story about the problem your code helps to share, and this story should be cohesive a
...more
”
― Unit Testing: Principles, Practices, and Patterns
― Unit Testing: Principles, Practices, and Patterns
“
Недостатньо того, щоб дані узгоджувалися з вашою теорією; вони мусять не узгоджуватися із запереченням вашої теорії
”
― How Not to Be Wrong: The Power of Mathematical Thinking
― How Not to Be Wrong: The Power of Mathematical Thinking
