Long time lurker, first time poster. Don’t know what it’s been with my job but spurred this rant.

  • moto@programming.devOP
    link
    fedilink
    arrow-up
    3
    ·
    1 天前

    “See, I shouted at the computer and it did what I wanted in seconds instead of months! Why can’t you do that, nerds?”

    It also doesn’t say “no” like those nerds keep doing

    AI writing unit tests? God help us all.

    Haha, like I said in the foot note. If you don’t like it, good! “This is not a good use case, let’s scrap it and move on” is a perfect thing to say here.

    It’s the only thing I could think to try it with that I could easily audit results for. It mostly works. But there are a few things it does that causes me to scrap results

    • It loves to mock dependencies, even idempotent ones that don’t connect to 3rd party dependencies
    • The verbiage for the test names doesn’t speak towards requirements and is more like “it works” and often includes the word “should”.
    • It sometimes likes to mock the Subject under Test, which is a huge no no

    Often though I can keep some of it and just scrap the bad parts. And if it causes me problems I’m happy to quit it. It’s not revolutionary. I’m just whelmed.