How We Reached 92% Coverage with GitAuto

How We Reached 92% Test Coverage with GitAuto We decided to dogfood GitAuto by using it on the GitAuto repository itself. The goal was simple: demonstrate whether we could really achieve high test coverage in a real production codebase. After 3 months, we hit 92% line coverage, 96% function coverage, and 85% branch coverage. Here's exactly how we did it and what we learned. The Setup: 5 Files Per Day, Every Day Our approach was straightforward: Enabled schedule trigger: Set GitAuto to run automatically every day 5 files per day: Configured to target 5 files each morning Weekends included: Tests ran 7 days a week Repository size: ~250 files total The math was simple: at 5 files per day, we'd need roughly 50 days (about 2 months) to cover the entire codebase. In reality, it took closer to 3 months because we refined our approach along the way, experimented with different file counts, and occasionally restarted files when we improved the system. The Daily Routine Every morning, GitAuto wo