Given, When, Then

Gherkin and other languages and frameworks directed to Behaviour-driven development [2] made mainstream the distinction between the different parts of a test: Fixture or setup (Given); Execution or exercise (When); Assertion or verify (Then). We developers don't like to write tests. We like to write code, real code! When imposed with the need of writing… Continue reading Given, When, Then


Anatomy of a solution

Every solution is meant to solve a problem. Some solutions solve the problem well, others don't. Some never get implemented. A friend of mine once called software ideas that never go anywhere as "vaporware": great ideas that vanished as fast as they appeared, into thin air as if it was vapor. My own "vaporware" I do… Continue reading Anatomy of a solution