refactoring - Bearded Programmer

Bearded Programmer

Sign in Subscribe

refactoring

A collection of 5 posts

Driving code design, through tests (IV)

Driving code design, through tests (IV)

In the context of TDD, tests that only exercise the unit level are some of the most restrictive tests you can write, especially if you are maintaining a 1-to-1 relationship between implementation code and test code.

Driving code design, through tests (III)

Driving code design, through tests (III)

The mechanics of Test-Driven Development are pretty easy to grasp, but the addition of a couple of heuristics will really make the practice sing.

Driving code design, through tests (II)

Driving code design, through tests (II)

The mechanics of TDD are pretty easy to learn, but take special care that your tests will be readable to Future You, who has to solve any issues with the code.

On tests and testing

Hello, gentle reader. Please allow me to rock your entire human face by dropping this truth bomb: > Tests are about more than testing. "Obviously!" you yell, your riposte ringing out triumphantly against what is seemingly a rather anemic statement. The truth bomb has failed to detonate. Your entire human face

Refactoring and clarity

TLDR > The purpose of refactoring is to improve code clarity. Introduction I refactored some code lately and I want to talk about it. Actually, let me back up and cover a few foundational points first, because without those it's going to appear like I'm ranting. Probably because I am. But