GitAuto

🚀 New release: You can now specify a parent issue

📝 New post: How to Detect Low Test Coverage Files in Jest

📝 New post: How to Detect Low Test Coverage Files in Flutter / Dart Through observing our customers' behavior, we've noticed a common challenge when teams want to improve their test coverage: identifying which files to tackle first. Without a clear overview of low-coverage files, developers often resort to randomly selecting files or relying on gut feelings. This initial hurdle of "where do we even start?" can significantly slow down or even halt test coverage initiatives, often leading teams to abandon the task entirely. That's why we're introducing this coverage dashboard. It provides an instant, clear view of which files need attention, eliminating the guesswork from test coverage improvement. In this guide, we'll show you how to set up automated test coverage reporting for your Flutter / Dart project and use GitAuto to improve coverage systematically.

🚀 New release: Enable GitAuto to run on the backend so that users can easily generage GitHub issues & PRs for files with low test coverage Flutter/Dart engineers can now add GitAuto to their repository, generate a test report from the GitAuto dashboard, view a list of files sorted by coverage in descending order, bulk-create GitHub Issues from them, assign them all to GitAuto, and instantly open pull requests with the missing test cases. With enough credits, they can even generate all the test cases in a single day. #Flutter #Dart #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