What exactly is refactoring? Is it just changing code? What does “not changing functionality” really means? Well, you’ve come to the right place. I’ve got just the webinar for you. And not only that, I’m going to show you how to refactor, even when you don’t have tests. If you Read more…
Ok, time to run the test. Well, that’s interesting. The test is not even running until the end, we’re crashing before it completes. Let’s see what’s wrong. Seems that this line breaks: List<Ingredient> fillingIngredients = new ArrayList<Ingredient>(ingredients.subList(1, ingredients.size() – 1)); when running the case where dish includes: Sauce = Pesto, Read more…
Last time we talked about flow analysis in the code. We figured out the cases we want covered. But, even for these cases, we don’t know what the expected result is. It’s worse than that in the real world. In our case, after we’ve drawn the boundary and decided which code Read more…
The current code version we’re talking about is tag 1.1. Last time, we have surrounded our code with a boundary, doing some early refactoring. We now know the entry points, and the exits are covered by interfaces, leaving code we don’t want to deal with outside our system. We can Read more…
Check out the original version of the code (Java, and also in C#, in tag 1.0). Right, time to move some code around. Before we do that, remember step #1 in our process: Draw a line around our tested code. For us it’s mainly the “cook” method. That’s the heart Read more…
Last time I gave you a sneak peak at our PastaMaker. You can check the whole project here. Let’s take a closer look. The main logic is in our PastaMaker, so focusing on testing it makes sense. Most of the logic is there, and so are the changes we need Read more…
As long time readers, you know that if we’ve got legacy code, we want tests for that. However, the code doesn’t always play along. As you’ll see in this example, this is the kind of code that really needs tests. It’s full of logic. It’s alive and working, and it’s Read more…
Other awesome posts in the series: So we talked about static constructors and how to go around them. How about instance constructors? Are they innocent or guilty of the same crimes as their static brothers? I think Java got the terminology right (although not the implementation). What we call a Read more…
The other posts in the series: Where we last left off, we discussed how to dismantle the static constructor (or initializer) booby traps. And I promised you an example. I’ll do that in C#, but the operations apply to any language that uses these constructs. Before I do that I’ll Read more…
Here is the rest of the gang: This time we’re going to tackle the most problematic issue in testing object-oriented languages. Obviously because constructors only exist in those, but also, because even power tools have problems handling them. But we’ll start where it hurts less. The evil static constructor Static constructors Read more…