legacy code | TestinGil

Should I Change My Code For The Unit Tests?

I don’t get tired of hearing that question, because if I did, I’d need to sleep for a couple of […]

I was honored to come back to JCON, and present “How to TDD in Legacy Code”. In Java of course.

Well that’s a new thing! Sort of new. Well, the session is not new. Everybody now does TDD in legacy

The current code version we’re talking about is tag 1.1. Last time, we have surrounded our code with a boundary,

Last time I gave you a sneak peak at our PastaMaker. You can check the whole project here. Let’s take

As long time readers, you know that if we’ve got legacy code, we want tests for that. However, the code

Really sorry it’s the last Let’s Test. Great fun! Anyway, here are the slides. [slideshare id=75994166&doc=betercodeforbettertests-170515180216]

This conversation comes up in every training I do about testing. I know exactly when it will happen. I know

When we talked about understanding what we’re actually testing in error handling, we talked about the ability to understand the