I once heard someone describe legacy systems as systems without test coverage. I think it’s not the best description, but it’s certainly an interesting perspective.
It’s part of why it bothers me when folks say they use LLMs to make unit tests. If anything, you should be writing tests by hands to get a solid specification then let the AI make the code. Of course this is a false dichotomy, but I’m just saying if you have to choose between those two options in some weird hypothetical bizarro world.
Not the best description doesn’t cut it, it’s just false description. I can easily write a system with 100% test coverage, bugged as hell and containing so many weird abstraction tricks that it takes a significant effort to figure out even what is happening in the simplest scenario. And yes, part of that hundred percent coverage is going to be llm style: test that something does what you already know it does
So… Just like any other legacy system you inherit.
I once heard someone describe legacy systems as systems without test coverage. I think it’s not the best description, but it’s certainly an interesting perspective.
It’s part of why it bothers me when folks say they use LLMs to make unit tests. If anything, you should be writing tests by hands to get a solid specification then let the AI make the code. Of course this is a false dichotomy, but I’m just saying if you have to choose between those two options in some weird hypothetical bizarro world.
Not the best description doesn’t cut it, it’s just false description. I can easily write a system with 100% test coverage, bugged as hell and containing so many weird abstraction tricks that it takes a significant effort to figure out even what is happening in the simplest scenario. And yes, part of that hundred percent coverage is going to be llm style: test that something does what you already know it does