The word “legacy” has a lot of connotations. Mostly bad ones. We seem to forget that our beautiful code gets to “legacy code“ status three days after writing it. Michael Feathers, in his wonderful book “Working Effectively With Legacy Code” defined legacy code as code that doesn’t have tests, and Read more…
It’s a funny thing, code testability. It’s not really defined, or rather, it is defined poorly. If “testable code” is “code we can test”, that means all code is like that. We can test it through unit tests. If it’s hard we can move to functional tests. And if all Read more…
Whenever we learn a new skill, and go deeper, it feels like we’re climbing a stairway to mastery. A few years ago, I described how people get into unit testing, and their journey along the path, as walking up a staircase. I’ve seen many people go through this. Our stairs Read more…
I was apparently mistaken when I said I’d publish small stuff over time. We’ll see how it goes. I’ve got a full chapter (so far) of Everyday Unit Testing: • Unit Testing Economics. – History – How did we get to where we are – Selling unit testing – the Read more…
Unit testing is a set of skills, that rarely appears on a resume. When I saw a resume with unit testing on it, it rose up to the top of the interview queue. I understood the person who put it there understands what it means to the business. If the Read more…
I’ve decided to do smaller releases of “Everyday Unit Testing”, and not wait for full chapters. I’m going to send out emails once a month with the accumulating changes, but releases would be more frequent. As to this one, this is a brief history about how developer testing (unit testing Read more…
You’ve probably seen it coming. I started a series of posts about unit test attributes here, and then went into them in details. I now morphed the series of posts into a section into the Basic Guidelines chapter. If the other sections I planned are going to be this long, Read more…
This is last, final, and 10th entry in the ten commandments of unit tests attributes that started here. And you should read all of them. We usually talk about isolation in terms of mocking. Meaning, when we want to write unit tests, and the code has dependencies, we use mocking Read more…
This is the 9th post in the Unit Tests Attribute series that started here. To learn more about testing, contact me. I keep hammering on trust and how it’s crucial that we trust our unit tests. If unit tests are deterministic, they raise the level of our trust. If the Read more…
This is the 8th post, soon to be the 8th wonder of the world, in the Unit Tests Attribute series that started here. To learn more about testing, contact me. I want to thank Steven Colbert for coining a word I can use in my title. Without him, all this Read more…