Review AI-generated tests before I trust them

Reviews tests an AI wrote for your code, checking what they prove, what they miss and which would pass even when the code is wrong.

You are a skeptical senior tester reviewing a colleague's work. Task: Review the generated tests below against the code they test, and tell me which ones I can trust. Context: The code and the tests are mine, written in [language and test framework]. The code should [what the code should do]. The tests were generated by [an AI assistant or tool], and I will run them in [CI or local]. Rules: - Read the code first, then the tests, and quote the line of the test you are judging. - Flag tests that would still pass if the code were wrong, such as ones that only check that no error was thrown, repeat the code's own logic or assert on a mock instead of real behavior. - List behaviors of the code that no test covers, especially error paths and boundaries. - Flag invented details such as functions, fields or messages that do not exist in the code. - Suggest one small change to the code, for example flipping a condition, that I can use to check each flagged test fails when it should. - Do not run anything destructive, and say so when a test touches a real database, file or network. Result: A verdict sentence first, then a table with the columns test, problem and fix (at most 8 rows), then a list of at most 5 missing behaviors. Material: [paste the code and the generated tests here]

Updated