You think I was finished? I haven’t even started. The first group of associated costs to testing were around the fact that unit tests are, in fact, code and as such are susceptible to all kinds of flaws that come Read more…
We talked about what we perceive as the cost of unit tests: slowing us down. That does not mean that unit tests are free. There are actual costs associated with unit tests, although they may not be what you think. I Read more…
Although ROI is dead it is still useful to talk about value and cost of witing tests. When we write automated tests, regardless of it being unit, integration, end-2-end, load test, or whatever kind, the cost we have in mind Read more…
Once more I get into a training session on unit testing, and once more I hear “It feels wrong to change my code just for testability.” My immediate reaction was “because the design you have right now is so good, Read more…
We tend to categorize different types of tests according to what they cover. Unit tests cover small portions of code, usually a method or a class, while we mock the rest of their interaction. Integration tests cover several components in Read more…
I know it’s been a while, but the Everyday unit testing book is not going away! I’ll try to pick up speed, while you can give me feedback on v.05 of the “Everyday Unit Testing” book. Here’s what’s new in Read more…
This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring steps before writing unit tests for legacy code, and how they make our life easier. Other posts include: In Read more…
This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring steps before writing unit tests for legacy code, and how they make our life easier. Other posts include: A few Read more…
This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring steps before writing unit tests for legacy code, and how they make our life easier. It continues the last post Read more…
This post is part of the “Legacy Code to Testable Code” series. In the series we’ll talk about making refactoring steps before writing unit tests for legacy code, and how they make our life easier. Other posts include: Adding accessors Read more…
