Let’s get to the point. I have this nice little piece of legacy code:
Here we are setting an Http Cookie, possibly considering a bunch of parameters, including setting an expiry date if provided.
We have also this function:
In this case we get the cookie given the name of it.
Not the worst code, yet not beautiful code, easy to follow and not many responsibilities going on. There is a problem though: there aren’t any unit tests covering it.
Some people may argue that it isn’t a problem. For me, it is. I don’t feel like I want to touch that code. It is in a shared library, if I fuck it up, I will probably make a mess, breaking some other stuff.
TDD is about workflow, Unit testing is about confidence. If I don’t have any unit tests around it, my confidence is, zero?
We all have had to change some code like this. In my case I have to provide a parameter so that when creating the cookie, it can be created as an httponly or not.
I’m planning to pass an optional parameter, isHttpOnly, and then doing something like:
Simple code, only an assigment. I’d really like to unit test my change, but this code is difficult to unit test.
The big deal is this line:
Probably I would have been a lazy guy and chunk my code in it. This time around it is different, I am doing Pair programming with Mahmut.
He acts as an angel on my shoulder, as a good friend telling me the things I should do, even if those things are hard to hear: even if my code if simple, I want to have confidence in my change.
Most importantly I want to apply the Boy Scout rule. Next time someone else lands in this code she will find some unit tests so that the campground will get cleaner and cleaner.
Ok, let’s try to unit test this code. How can I solve the problem of having the static HttpContext? How can I unit test it?
We could create an addapter for the HttpContext and mock it in our unit tests.
It isn’t easy in this case since the whole class is static:
We can’t inject an addapter through the constructor. We shouldn’t either do method injection, that would mean introducing some breaking changes, this is a nuget package used in god knows how many places.
Ok, I’ll figure this out. Let’s write a unit test:
This is the important bit:
Wait a second, you told me we couldn’t inject anything to avoid breaking changes.
That’s right, but let’s go to the method:
I see… you have changed the existing method from public to internal, what about the public method?
Here you have it, in the same class:
So if you see the public method calls the new internal method that holds all the legacy code. The public method sends an anonymous function providing the actual HttpContext.
In our test we pass an anonymous function providing the fake http context:
Now we see some tests around the legacy code. I have some confidence in my code and the next person touching this code will find some ground where she could write her tests.
Thanks Mahmut for pushing the quality of our code and pushing me towards becoming a better developer.
Now I can send this to code review without the shame of having to explain why I didn’t write any unit tests.