| ▲ | locusofself 2 hours ago | ||||||||||||||||
Not using AI to at least writes tests in this day and age is crazy work. I started a desktop application 2 months ago and it has almost 3,000 tests now, MANY of them UI tests. | |||||||||||||||||
| ▲ | timcambrant 2 hours ago | parent | next [-] | ||||||||||||||||
AI is a bit too excellent at writing tests. The number of tests doesn't really convey any information on test coverage. At least I've found that agents that naively improve codebases will write tests for pretty much anything, including irrelevant behavior that has little value in ensuring stability, security or correct behavior. It would probably help to run a test review stage with a strong model, where agents attempt to correct and consolidate tests to guard behavior rather than ensuring that theoretical code paths are followed. | |||||||||||||||||
| |||||||||||||||||
| ▲ | HiPhish an hour ago | parent | prev | next [-] | ||||||||||||||||
Using AI to write tests in this day and age is crazy work. The machine is great at writing tests, but the quality of the tests is awful. It will write redundant tests, it will write tests that assert too many thing in one, it will not write tests that need to be tested. It's the part where I have to clean up the most every time. Quantity is not quality, and you really don't want to skip on the quality of your quality assurance. I'm writing a React + Django full-stack application, so there should be more than enough training data out there. | |||||||||||||||||
| ▲ | ares623 2 hours ago | parent | prev [-] | ||||||||||||||||
Look, guys, you are literally allowed to fork and go ham on the code. | |||||||||||||||||
| |||||||||||||||||