testing – Page 10 – Türker Yıldırım

Branch coverage at 100%, and meaningless

NoteDecember 30, 20231 min read

Every branch executed, and no assertion that any of them produced the right answer. The assertTrue(true) is the tell, and it exists because a test with no assertions…

Block hooks, and the plugin that inserts itself

Deep diveDecember 21, 202310 min read

6.4 in November, and a plugin that can insert a block without editing a template. Install instructions that said “now edit your footer”.

The Randomizer, and rand() in a test that must be stable

NoteDecember 21, 20232 min read

A test using shuffle() that failed roughly once a fortnight, and a global seed that could not be set without affecting everything else. The Randomizer arrived in 8.2…

A fixture builder instead of a fixture file

NoteDecember 19, 20231 min read

A JSON fixture of a full order, loaded by 40 tests, where each test cared about two fields and was coupled to the other thirty. The fixture file…

Typed class constants, and the interface that had been lying

Deep diveDecember 7, 202310 min read

8.3 on 23 November, and a constant can finally declare a type. An interface constant documented as a string, implemented as an int in one class.

A module boundary that is a directory and a test

NoteDecember 6, 20231 min read

A boundary everybody agrees on and nothing checks is a boundary that will be crossed within a fortnight. A directory is a convention and a test is a…

The method that stopped overriding anything in 2019

Deep diveDecember 5, 202310 min read

#[Override] in 8.3, and what it asserts. A subclass method dead since a parent rename four years ago, with a bug report closed as not reproducible.

The test that failed only when run alone

NoteNovember 21, 20232 min read

The usual failure is a test that passes alone and fails in the suite; this was the reverse, and the reverse is more interesting. A test that depends…

The interface with one implementation, and when that is fine

Deep diveNovember 16, 202310 min read

140 interfaces, 128 of them with exactly one implementation, and a jump-to-definition that always lands on the wrong file.

A snapshot test for an email, and the day it caught something

NoteNovember 13, 20232 min read

Snapshot tests are usually a way of asserting that nothing changed, which is worth very little, until the change is one nobody intended. The snapshot caught a currency…