GitAuto Logo
  1. Home
  2. Pricing
  3. Docs
  4. Dashboard
  5. Blog
  6. Contact
  1. Home
  2. How It Works
  3. Use Cases
  4. Pricing
  5. Docs
  6. Dashboard
  7. FAQ
  8. Blog
  9. Contact

Coverage Dashboard

Learn how to use GitAuto's Coverage Dashboard to identify and improve low test coverage in your codebase.

Coverage Dashboard

Requirements

To use GitAuto's coverage analysis:

  • Coverage report must be in LCOV format
  • Report file must be named lcov.info
  • Report must be uploaded as GitHub Actions artifact named coverage-report
  • Your project uses GitHub (GitAuto is a GitHub App)

Language & Framework Support

GitAuto is language and test framework agnostic. Any programming language or testing framework that can generate LCOV reports is fully supported.

This means GitAuto works with any language or framework including Python, JavaScript, Java, Go, PHP, Ruby, C#, Rust, and many more. Any testing framework that generates LCOV reports is supported - pytest, Jest, JaCoCo, go test, PHPUnit, RSpec, xUnit, Cargo test, and others.

We provide detailed configuration examples for popular combinations to help you get started quickly:

Python

pytest and other Python test frameworks

JavaScript / TypeScript

Jest, Vitest, and other JavaScript / TypeScript test frameworks

Java

JaCoCo with Maven or Gradle

Go

Go's built-in test coverage tools

PHP

PHPUnit with Xdebug or PCOV

Ruby

RSpec with SimpleCov

Flutter

Flutter's built-in test framework

Multi-Language

Repositories with multiple languages (e.g., PHP + JS)

Dashboard Features

From the Coverage Dashboard, you can:

  • View files with low test coverage
  • Select specific files for improvement
  • Create GitHub issues individually or in bulk
  • Assign issues to GitAuto for automated improvement
  • Track progress over time with Coverage Charts

Automated Improvements

Once issues are created and assigned to GitAuto, it will:

  1. Analyze the code in files with low coverage
  2. Generate appropriate test cases
  3. Create pull requests with the new tests
  4. Verify coverage improvements

Coverage Reports Not Showing Up?

Don't worry, we've all been there! LCOV setup can be tricky, and every testing framework has its quirks. Let's get your coverage dashboard populated with real data so you can start improving your tests.

Contact us and we'll help you debug it together!

InstallationJavaScript / TypeScript Coverage

Getting Started

  • Installation
  • Setup

Triggers

  • Overview
  • Schedule Trigger
  • Test Failure Trigger
  • Review Comment Trigger
  • Dashboard Trigger

Coverage Dashboard

  • Overview
  • Python Testing
  • JavaScript Testing
  • Java Testing
  • Go Testing
  • PHP Testing
  • Ruby Testing
  • Flutter Testing
  • Multi-Language
  • Coverage Charts

Customization

  • Repository Rules
  • Output Language
  • GITAUTO.md

Integrations

  • CircleCI Integration
  • npm Integration

How It Works

Context Enrichment

  • Line Numbers
  • Full File Reads
  • Test File Preloading
  • Test Naming Detection
  • Error Baselines
  • CI Log Cleaning
  • Trigger-Specific Prompts
  • Coding Standards

Output Auto-Correction

  • Diff Hunk Repair
  • Diff Prefix Repair
  • Tool Name Correction
  • Tool Argument Correction
  • Import Sorting
  • Trailing Space Removal
  • Final Newline
  • Line Ending Preservation
  • Sanitize Tool Arguments
  • Lint Disable Headers

Quality Verification

  • Formatting
  • Linting
  • Type Checking
  • Test Execution
  • Coverage Enforcement
  • phpcs / phpstan Support
  • PHPUnit Support
  • pytest Support
  • Snapshot Auto-Update
  • Untestable Detection
  • Should-Skip Detection
  • Dead Code Removal
  • Quality Check Scoring
  • Quality Checklist

Safety Guardrails

  • File Edit Restrictions
  • Temperature Zero
  • PR/Branch Checks
  • Race Condition Prevention
  • Bot Loop Prevention
  • Webhook Deduplication
  • Duplicate Error Hashing
  • Infrastructure Failure Detection
  • Strict Tool Schemas
  • No-Change Detection

Token/Cost Management

  • Token Trimming
  • Outdated Diff Removal
  • Stale File Replacement
  • Skip CI Intermediate
  • CI Log Deduplication
  • Web Fetch Summarization
  • Context Forgetting
  • File Query Routing
  • On-Demand Diff

Resilience & Recovery

  • Model Fallback
  • Overload Retry
  • Forced Verification
  • Error Files Editable

Hallucination Prevention

  • Web Search
  • URL Fetching
  • Anti-Hallucination Prompts
  • GITAUTO.md Restrictions
  • Review Response Guardrails

Ready to improve your test coverage?

Go from 0% to 90% test coverage with GitAuto. Start for free, no credit card required.

Install FreeContact Sales

Product

  • Home
  • Why GitAuto
  • What GitAuto Does
  • How It Works
  • Use Cases
  • How to Get Started
  • Solution
  • Pricing
  • Pricing Details
  • ROI Calculator
  • ROI Methodology
  • FAQ
  • Blog
  • Contact

Dashboard

  • Dashboard
  • Coverage Trends
  • File Coverage
  • Credits
  • Open PRs
  • Usage
  • Triggers
  • Actions
  • References
  • Rules
  • CircleCI Integration
  • npm Integration

Documentation

  • Docs
  • Getting Started
  • Setup
  • Triggers
  • Coverage Setup
  • Customization
  • How It Works
  • Auto Merge
  • CircleCI
  • npm

Legal

  • Privacy Policy
  • Terms of Service

Connect

  • GitHub
  • LinkedIn
  • Twitter
  • YouTube
GitAuto Logo© 2026 GitAuto, Inc. All Rights Reserved