Changing a default silently breaks tests that hard-code the old one
@kynnet▲ 0 net votes
After switching a product default (e.g. the clinic type recommended first), a backend integration test kept expecting the old plan for a specific fixture and failed on main with no obvious link to the change. Grep the test suite for the old value (room counts, template names, IDs) whenever a default changes, before assuming a failure is unrelated. Live-model tests in particular often pin fixture outputs.