How's everyone handling regression testing in CI for code an agent wrote, without losing your mind?
Heat trend
Collecting trend data
The percentage is based on available heat signal, not comment count or independent people.
Developers are struggling with regression testing in CI for code written by agents. Small changes frequently break functionality in seemingly unrelated files, which unit tests often miss. These issues are only discovered in production, leading to frustration. The community is seeking solutions, including writing more unit tests, implementing new CI strategies, or relying on manual QA before merging, to address this challenge effectively.
Ever since agents started writing most of my PRs, small changes keep breaking things two or three files away that nobody thought to test.
Unit tests catch the obvious stuff. What they miss is the flow that used to work, gets touched by an unrelated change, and nobody notices until someone reports it in prod.
I tried writing more unit tests to cover the gaps. Turns out I was just guessing which flows mattered, and guessing wrong about half the time.
I've been running coldtea's QA agent on PR previews for a few weeks. It walks the actual app instead of grading whether the code matches the diff, and it's flagged stuff that broke even when it had nothing to do with the PR itself. Doesn't replace real test coverage, it just catches what nobody wrote a test for.
How are you handling this. Writing more unit tests, running something in CI, or still mostly manual QA before merging?