clickable link https://www.jungsteven.com/blog/2024-07-03-past-present-future-mutation-testing https://www.jungsteven.com/blog/2024-07-03-past-present-futu...

clickable link https://www.jungsteven.com/blog/2024-07-03-past-present-future-mutation-testing https://www.jungsteven.com/blog/2024-07-03-past-present-futu... Every place I have worked required showing that tests worked during code review, break the code, watch the tests fail, unbreak the code, watch tests pass. If I were going to spend resources on making testing better and my choice was between mutation testing and property testing, I'd rather spend that energy on property testing. Mutation testing feels like something that the test framework should be doing anyway, maybe not every run, but every time it sees a new test. If you keep going in this direction, your LLMs will be expert vulnerability injectors, possibly your end goal. All technologies are dual-use.