466
I know I should... but I just really don't wanna (programming.dev)
submitted 3 years ago by to c/programmer_humor@programming.dev
52 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 3 years ago (3 children)

Writing good tests is foxtrotting hard, don't kid yourself.

Writing good tests that are actually readable and thoroughly exercise the code under test is damn near impossible.

Send help.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 4 points 3 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    I've never done automated UI testing. Honestly, I'm afraid to.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent