Back at it again, this week we will cover chapter 9 of the book titled "I can't get this class into a test harness". Sometimes it's just hard. But if it were easy then everyone would do it!! Okay, I'm sorry that
In legacy code, one of the most important considerations is that we don't have tests around much of our code. What's worse, is that getting them in place is difficult. That's why many people are tempted to go back to the techniques we learned
How long does it take for you to make a change? If I ask this to 100 different people, I will get 100 different answers. The answer varies widely. So in projects with unclear code, many changes take a long time. On the other hand, in clearer areas, this can
You might ask me? Is doing all this additional work worth it? Do I need to test all my code? Do I need to break all these dependencies? You might be wondering whether it’s worth doing these things right now. The truth is, the work that you do to
When people first start writing tests, they will notice how horrible code is structured for them. In general, this is true most of the time, except when you write tests along with the code which is called Test Driven Development. I personally think it's a thing that every
In the last chapter, we covered the refactoring process. We declared that the most important step in refactoring is testing. So why don't people write more tests? The simple answer is because it's hard. The reason why it's hard is because of dependency management.
In this chapter, we will cover the different ways changes happen in our system. In general, there are two ways: * Edit and Pray * Cover and Modify Unfortunately,Edit and Pray is industry standard. The process of Edit and Pray goes like this: 1. Carefully plan the changes you are going
> “Legacy Code is code without tests” That's pretty much the premise of the whole book. Thanks for reading... Just kidding, there's a lot more to this. Testing is one of those things that I've ignored for a good portion of my career but