For some codebases I think tests breaking at every change is the expected behavior. In a way it gives an approximation of the dependency graph of the code work

For some codebases I think tests breaking at every change is the expected behavior. In a way it gives an approximation of the dependency graph of the code worked on, and acts as a reminder of the other functionalities that one might not have intended to touch.