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

Block locking, and the page an editor cannot break

Deep diveJune 29, 20229 min read

6.0, and locking that is per block rather than per template. templateLock all was too much and nothing was too little.

The deploy that needed a database restore

Deep diveJune 7, 202215 min read

A migration that wrote bad data to 41,000 rows. Rollback restores the code and not the rows.

The report that ran on a replica and was three minutes stale

Deep diveMay 31, 202210 min read

Read routing added for capacity, and a report that disagreed with the dashboard. Two numbers, both correct, three minutes apart.

Asserting an event was dispatched, not that a mail was sent

NoteMay 31, 20221 min read

Testing the effect couples the test to the listener, and testing the event tests the thing the code under test is actually responsible for. The listener gets its…

A load test with an assertion is a test; without one it is a benchmark

NoteMay 26, 20222 min read

A load test that reports numbers requires somebody to interpret them; one that asserts a threshold fails a build. The ramp shape matters as much as the target:…

A feature flag needs an expiry date at creation

NoteMay 19, 20222 min read

Creating a flag is a deliberate act and removing one is not, so without a mechanism the count only goes up. A failing test is the only mechanism…

Style variations, and the theme that ships four designs

Deep diveMay 18, 202210 min read

6.0 in May, and styles/ as a directory of theme.json fragments. Four client sites that differ only in colour and type.

An SLO that survived contact with the business

Deep diveMay 17, 202214 min read

99.9% was written in a document in 2020 and had never been measured. Three teams with three definitions of “up”.

Sharded pub/sub, and the cluster that could not broadcast

Deep diveApril 25, 20229 min read

A broadcast that goes to every node on every publish. Classic pub/sub does not scale in a cluster, and 7.0 gives channels that respect slots.

Playwright traces uploaded only when a test fails

NoteApril 20, 20221 min read

A trace is large and is only interesting when something went wrong, so recording on retry and uploading on failure is the arrangement that stays affordable. if: failure()…