> Unit tests are generally much harder to understand and need to be changed much more frequently. Changed more frequently, yes. Harder to understand is usuall

> Unit tests are generally much harder to understand and need to be changed much more frequently. Changed more frequently, yes. Harder to understand is usually because they're not-quite-unit-tests-claiming-to-be. Eg: a test for function that mocks some of its dependencies but also does shenanigans to deal with some global state without isolating it. So you get a test that only test the unit (if that), but has a ton of exotic techniques to deal with the globals. Worse of all worlds. Proper unit tests are usually just a few line long, little to no abstraction, and test code you can see in the associated file without dealing with code you can't see without digging deeper.