GitAuto

?? New release: Enable users to know test coverage report on GitAuto dashboard, grasp where to improve file by file, and open GitHub issues for selected ones GitAuto is a QA coding agent. The GitAuto's Coverage Dashboard is a new tool that displays test coverage data for repositories where GitAuto is installed. It helps users create GitHub issues for improving test coverage. The help content outlines four main steps: 1. Select Repository: Users need to choose an Organization and Repository to begin. 2. Refresh Coverage: First-time users should click the "Refresh Coverage" button in the Actions menu. 3. Wait for Analysis: The system takes 5-10 minutes to: - Clone the repo - Install packages - Build the project - Run tests - Generate and analyze test reports - Show coverage data

?? New release: Enhance the log feature to maintain a historical record of GitAuto's actions, enabling users to easily track all activities performed by GitAuto on their behalf.

?? New post: How to Add Widget Tests with a QA Coding Agent for Flutter

?? New post: How to Set Up Automated Tests with a QA Coding Agent for Flutter Wrote the first part of a series on how to use GitAuto, the AI QA engineer, to see how much we can automate test case creation for a client who's a pro at using various AIs, not just Copilot. This one's all about setup.

?? New release: Enable GitAuto to read all lines of a file if it's within 100 lines. For files exceeding this limit, read only the specified section along with 50 lines before and after when line numbers are provided. Background: When GitAuto rummages through files in a repository, it assumes the files are large and allows specifying line numbers to reduce noise. However, due to a quirk—possibly related to the o3-mini model GitAuto uses—it sometimes unnecessarily specifies the first line. In such cases, GitAuto should read all lines, just as it would when no line numbers are specified.

?? New release: Enable GitAuto to search specific file contents up to N times

?? New post: How to Add an Automated Unit Test with a Coding Agent

?? New post: How to Fix an Error within Minutes with Sentry and GitAuto When a bug pops up, what do you do? Fix it? Ignore it? Does your logging tool catch it? Or do you only find out when a customer complains? But, hey, the stuff you gotta do this week doesn't change, right? Wouldn't it be awesome if you could whip up a fix PR as soon as a bug hits? Error logs aren't always clear, can mislead, and often don't reveal the cause, so you can't say you'll fix everything 100%. Still, it might cut down the initial investigation big time. So, we ran an experiment combining a logging tool with an AI Coding Agent to see if we could create a fix PR right after a bug shows up.

?? New post: How to Add Integration Tests Using an AI Coding Agent Back in the day, when manual testing was the norm, folks would spend ages crafting test specs in Excel and have someone else review them. But when it came time to actually run the tests, they'd often be short on time or things wouldn’t go smoothly. This led to fudging results since everything was manual. This kind of thing was common, and there were constant inquiries into why these fudging occurred and how to prevent them. Now? Automating tons of tests and running them instantly is a breeze. I wrote an article showing how you can use an AI coding agent, GitAuto, to whip up integration test PRs in minutes, run those tests immediately, and keep them running continuously going forward. If you're in a similar boat, give it a shot.

?? New release: Enable GitAuto to read the parent issue number, title, body too in addition to an issue when working on the issue. GitAuto can now reference the parent issue’s number, title, and body