I'm working on a ticket at the moment that involves a lot of refactoring work to support a new feature. In the initial run on this code base we went a bit unit

I'm working on a ticket at the moment that involves a lot of refactoring work to support a new feature. In the initial run on this code base we went a bit unit test crazy, which was fine at the time, but I'm seeing the drawbacks now where I'm doing a lot of surgery on the components. I've ended up just beefing up the current integration tests with some extra edge case testing and, after the refactoring work, they still pass, which has given me a lot more confidence. I think a lot of this comes to head when you unit test the glue logic that orchestrates the entire program, unit testing those becomes painful with mocks etc because they become fragile whenever you do any refactoring work. I'm not sure what to think really.