Timing and tests, name a better migraine duo :D.

We continuously create tests that ensure a process completes in an set amount of time, and every time, we don't give them enough leeway, and the test will fail randomly if the CI runner gets overloaded.

int add(int a, int b) {
    return a + b;
}

This code is clearly functional, it'll compile and execute.

However, the customer actually needs the code to do a saturating add.

With that knowledge, we can clearly see that the code is not correct. It will not saturate, it will wrap around instead.

Without that knowledge, an LLM will happily write some basic unit tests that won't cover the saturation edge case, and the bug would live on until its hit in prod.

If you're lucky, and your function doco is good, the LLM might spot the bug, and notify you.

My personal preference for how to generate tests is to ask the agent to write specific tests. E.g: "write a test for add that demonstrates that it saturates".