I read about mutation testing in a course of test oriented programming. And i am unsure to this day of what domain it's meant for.

The most strict and safety critical code i have encountered, was specifying its system behaviour in a state machine diagram of a ISO specification.

Yet it was too state based for effective unit testing. Instead it opted to assert the living hell out of the codebase and be paranoid about even the stability of the ram it wrote to.

I have a hard time imagining a domain that is both;

1. Easily to coverage test to a high enough degree that mutating testing can be used.

2. Needs pedantic testing to the point of absurdity, perhaps already using boundary value diagrams for its test-cases.

And so mutating testing feels quite odd to me, and selling it as an AI tooling is even more insane. It feels like far more effort than to just not use AI.