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 is the cost the actual “writing tests”. You know, typing. 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, right?” (yes, I said it out loud). Let’s break it 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 concert, and then mock the other boundaries. System tests and 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 this increment: I’ve added a new section under “Writing tests” 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 the last post, I’ve talked about Extract Class refactoring pattern, 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 years ago I got this from Erik Talboom: “A private 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 on accessors. Other posts include: We talked about refactoring 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 to private state data is an admission that either our 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 included: As with renaming, extracting a method helps us understand legacy code better. 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 tests for legacy code, and how they make our life easier. Other posts include: Renaming is easy and is usually safe refactoring. Most IDEs have the refactoring Read more…