The Developer Changed the Feature. Who Fixes the Test?: read the article
If the developer who changed the behaviour does not fix the broken test in the same pull request, you do not have a test suite. You have a backlog with a CI badge.
6 min read
If the developer who changed the behaviour does not fix the broken test in the same pull request, you do not have a test suite. You have a backlog with a CI badge.
6 min read
Read article: The Developer Changed the Feature. Who Fixes the Test?Series
Guided series through the journal — foundation articles build the core skill, challenge articles push into senior-level depth. Track your progress, earn certificates, and prove what you know.
Recently published
If the developer who changed the behaviour does not fix the broken test in the same pull request, you do not have a test suite. You have a backlog with a CI badge.
6 min read
A test written by the same agent that wrote the code confirms what the code does, not what it should do. Why a green, agent-authored suite says little about intent, and how to audit it.
9 min read
Playwright 1.63 adds named test locks for shared resources. They solve the scheduling half of the shared-state problem. The state itself is still yours to isolate.
6 min read
"Is this suite actually helping?" is a fair question that most teams cannot answer. A field note on instrumenting one suite for four weeks, and the metrics that changed the conversation.
5 min read
Not every check deserves to exist. A working method for ranking automation candidates by the decisions they serve, and for saying no to the rest.
6 min read
Test levels are a design tool, not a conference-talk taxonomy. This deep-dive lays out what each level actually buys you, and a decision rule for where every check should live.
6 min read