So so many unit tests I see don’t meaningfully test anything. It would be faster to just read the unit under test because the test itself presents nothing that you wouldn’t instantly recognize. Or the test is so tightly coupled to some arbitrary property that of course the test fails whenever you change something. UI tests at my current place are terrible for this, as they’re just comparing DOM structures so any change breaks it.
It’s not the worst thing. Like any other test there are more and less valuable methods. Imo, the hardest part is not coupling yourself to the incidental. All tests have that issue but UIs are almost entirely incidental. Styles, layout, and even data and function can be incidental and thus likely to change.
So so many unit tests I see don’t meaningfully test anything. It would be faster to just read the unit under test because the test itself presents nothing that you wouldn’t instantly recognize. Or the test is so tightly coupled to some arbitrary property that of course the test fails whenever you change something. UI tests at my current place are terrible for this, as they’re just comparing DOM structures so any change breaks it.
I’ve never done automated UI testing. Honestly, I’m afraid to.
It’s not the worst thing. Like any other test there are more and less valuable methods. Imo, the hardest part is not coupling yourself to the incidental. All tests have that issue but UIs are almost entirely incidental. Styles, layout, and even data and function can be incidental and thus likely to change.