Hacker News Reader

Easier said than done :-)

Tests might cover more code than a single unit owned by different teams, thus end up with multiple owners. Prefer "squads" as the owners rather the individuals.

But just like documentation the ownership might be stale and out of sync. So the idea would be let some reds in SLO dashboard correct them over time. It's not possible to automatically link "tests" to the "code" always.

View on HN

End-to-end tests might get tricky. But unit tests should be owned by the person/team/squad that owns the unit.

And unit tests should never break/be red. If the code needs to changed, the test needs to be changed at the same time.

End-to-end tests can be flaky. Those probably shouldn't prevent deployments and can be red for awhile. Should probably manually confirm if the test is acting up, there's a change in behavior, or if something is legitimately broken before ignoring them though.

Reply on news.ycombinator.com