← Back to context

Comment by giveita

3 days ago

The usefulness is in saving time boilerplating, plus figuring out tests I may not have thought of.

But I do closely review the code! It turns the usual drudge of writing tests into more of a code review. Last time I did it it had some mistakes I needed to fix for sure.

There shouldn't be boilerplate in test code. It should be refactored into harnesses, utils, and fixtures instead.

  • While absolutist, I think this is a good goal! AI wont do that unprompted. It will get the job done TM. But not elegantly.

    A lot of the tests have those things. Boilerplate becomes knowing which to use, as well as the it.each(...) etc. ceremonies

  • I'm not disagreeing per se, but in my experience my tests are so disposable they're never worth investing that much engineering effort in past getting them to pass