Menu

Refactoring towards testability

Published on August 07, 2018 and filed under Software engineering
Written
by Wouter Sioen and will take

15 minutes

of your time.
In short
Badly written code can be extremely hard to test. Let's take a look at some clear anti-patterns of untestable code and create strategies to get rid of them.

Want to see more articles like this in your inbox? You know what to do.

Written by

Wouter Sioen

Wouter looks like the nice kid you knew at high school. But boy oh boy, when it comes to problem-solving, this developer is like a pitbull on steroids.

Learn more about Wouter Sioen

Related articles

Grandfathering in legacy

Grandfathering in legacy

Maarten Scholz

April 16, 2020

Improving code style when working on a legacy code base

Improving code style when working on a legacy code base

Hannes Van De Vreken

April 27, 2015

Pointers and tips: dispelling the magic of git merge

Pointers and tips: dispelling the magic of git merge

Zvonimir Spajic

May 18, 2020