4 ms·
Knee jerk reaction is to hate this, but if the PRs are small enough to quickly review and/or fix, having your test suite start to execute branches of code that
by corytheboyd 2y ago
Knee jerk reaction is to hate this, but if the PRs are small enough to quickly review and/or fix, having your test suite start to execute branches of code that it previously wasn’t has some value? It seems much (or exactly?) like using copilot— it’s going to be wrong, but sometimes it is 80% there nearly instantly, and you spend all of your time on the last 20%. Still, time saved, and value gained, so long as you know what you are doing yourself. Maybe at least annotate the bot tests to not mix them in with the intentionally added human tests, then it’s even harder to justify throwing this idea out completely.
Even if the test is COMPLETELY off, it might be enough to get someone thinking “but wait, that gives me enough of an idea to test this branch of code” or even better “wait, this branch of code is useless anyway, let’s just delete it”
- plagiarist 2y agoI'd be worried that the tests it generates would be brittle or not helpful, like testing an exact implementation instead of the API contract. I don't know if that's the case here. I looked at the diff but I don't understand the code in the project. I'd like to see it on something I recognize better.