Tell me about your testing strategy when the assistant wrote the code.
A strong answer gets correlated blind spots, that the generator can't be the only author of its own verification, and builds the tests around independence
I always ask for tests along with the implementation, and then I review both. The tests need to cover the main functionality, the edge cases, the error handling. I add whatever cases the model missed, especially around boundaries. Everything runs locally before it goes into a PR, and then CI runs the full suite again anyway. One thing I do check is whether the tests assert meaningful behavior, because generated tests sometimes only check that a function returns something. Coverage tools help me confirm the new code is actually exercised. The bar is the same as for human code, really. If the tests wouldn't catch a regression they're just decoration, so I make sure they genuinely pin down the behavior.