The Full Automation Cycle
Not just test writing. GitAuto handles the entire workflow from detection to merge - then does it again tomorrow.
Detect untested files
Imports coverage reports from CI artifacts. Any file not at 100% line, branch, and function coverage is a target.
Learn existing patterns
Reads your test files to learn conventions - frameworks, assertion styles, mocks, and directory structure.
Open a pull request
Creates a PR with a clear description and coverage report links. Zero manual work.
Write or update tests
Generates test code following your repo's patterns. Creates new files or adds cases to existing ones.
Run CI pipeline
Waits for GitHub Actions, CircleCI, or any CI. Reads the full logs to understand what happened.
Fix test failures
Reads CI logs, identifies root cause, fixes test failures, ESLint errors, and type checker warnings. Repeats until green.
Address reviews
Responds to human and bot reviewers. Resolves requested changes and code review feedback.
Sync branch
Updates the PR branch when other PRs get merged. Resolves merge conflicts if they happen.
Merge auto or manual
Auto-merges when all checks pass and only test files are changed, or you merge manually. Then starts the next file from step 1.
Detect untested files
Imports coverage reports from CI artifacts. Any file not at 100% line, branch, and function coverage is a target.
Learn existing patterns
Reads your test files to learn conventions - frameworks, assertion styles, mocks, and directory structure.
Open a pull request
Creates a PR with a clear description and coverage report links. Zero manual work.
Write or update tests
Generates test code following your repo's patterns. Creates new files or adds cases to existing ones.
Run CI pipeline
Waits for GitHub Actions, CircleCI, or any CI. Reads the full logs to understand what happened.
Fix test failures
Reads CI logs, identifies root cause, fixes test failures, ESLint errors, and type checker warnings. Repeats until green.
Address reviews
Responds to human and bot reviewers. Resolves requested changes and code review feedback.
Sync branch
Updates the PR branch when other PRs get merged. Resolves merge conflicts if they happen.
Merge auto or manual
Auto-merges when all checks pass and only test files are changed, or you merge manually. Then starts the next file from step 1.
What this replaces
Without GitAuto, an engineer does every step manually: find untested files, study patterns, write tests, open a PR, wait for CI, debug failures, respond to reviews, and keep iterating. Even with AI coding tools, this takes about 2 hours per file.
See the ROI Calculator to estimate what this saves for your team.