Yeah creating tests for every single method is insane. If a feature changes it's more difficult you either have to figure out how to implement the change without changing the method, or you change the method and have update the unit test. But if you're constantly updating the unit tests, how do you know if you might've broken something else that the test was intended for.

It's way better just to do integration tests that match the feature request. That way the feature that someone asked for will continue to work even if you decide to refactor the code.