Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qlty.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
Coverage Report page

December 1–4, 2025 Full visibility into how each commit’s coverage report was built — and a way to clean it up when something goes wrong. Qlty Cloud now includes a Coverage Report details page for each commit, showing summary metrics and every upload that contributed to the report. Project admins can also delete individual reports or uploads from Coverage Settings when a bad upload needs to be removed.

​
Coverage page redesign

December 19, 2025 A clearer view of how a pull request moves your coverage. The Project Coverage page has been rebuilt from the ground up, with:
  • Improved stats cards
  • A Files Changed tab with rendered file diffs
  • A Components tab showing per-Component coverage for the pull request
  • A collapsible sidebar with coverage comparison details

​
Coverage summary comment improvements

December 5–12, 2025 Coverage summary comments on pull requests have been redesigned. The new comment includes:
  • An updated rating display
  • A Modified Components section showing which Components changed in the pull request
  • An AI prompt section with a ready-to-paste prompt for your AI coding agent to write the missing tests
  • The Qlty header image and clearer formatting

​
Maintainability shown as effort duration

December 1, 2025 Maintainability is now displayed as estimated remediation effort (e.g. “2h 30m”) in addition to issue counts, making it easier to compare projects and plan remediation work.

​
Jenkins CI auto-detection

December 26, 2025 We now support automatic detection of build metadata from Jenkins. Uploading coverage from a Jenkins build only requires the path to the coverage data file. See setting up coverage with Jenkins for the full walkthrough. 
qlty coverage publish coverage.lcov

​
More coverage formats supported

December 10–12, 2025 The Qlty CLI now ingests two more coverage report variants without any conversion step:
  • Apple’s xccov-json format produced by xccov from Xcode coverage data
  • JaCoCo reports containing <group> elements, the standard output for multi-module Maven and Gradle projects