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.

qlty coverage publish [OPTIONS] [PATHS]...
Upload coverage reports to the Qlty Cloud The qlty coverage publish command uploads code coverage reports to Qlty Cloud for analysis. It supports multiple report formats to ensure compatibility with various programming languages, including simplecov, clover, cobertura, coverprofile, lcov, jacoco, and the generic qlty format. Beyond uploading reports, this command allows the addition or removal of file path prefixes, tagging uploads for easier identification, and overriding the value of certain git-related variables. It integrates code coverage data into Qlty Cloud, offering a comprehensive view of your codebase’s coverage.

Arguments

One or more paths to the coverage reports to be uploaded
Do not upload the coverage report, only export it to the output directory
The format of the coverage report to transform. If not specified, the format will be inferred from the file extension or contents [possible values: simplecov, clover, cobertura, coverprofile, lcov, jacoco, qlty]
A tag to associate with this coverage report upload
Override the build identifier from the CI environment
Override the branch from the CI environment
Override the commit SHA from the CI environment
Override the pull request number from the CI environment
Override the git tag from the CI environment
Do not validate coverage data before publishing
The prefix to add to file paths in coverage payloads, to make them match the project’s directory structure
The prefix to remove from absolute paths in coverage payloads to make them relative to the project root. This is usually the directory in which the tests were run. Defaults to the root of the git repository
The token to use for authentication when uploading the report. By default, it retrieves the token from the QLTY_COVERAGE_TOKEN environment variable
The name of the project to associate the coverage report with. Only needed when coverage token represents a workspace and if it cannot be inferred from the git origin
Print coverage
Verbose
Suppress all output except for errors
The total number of parts that qlty cloud should expect. Each call to qlty publish will upload one part. (The total parts count is per coverage tag e.g. if you have 2 tags each with 3 parts, you should set this to 3)

Example

Upload a Cobertura report to Qlty Cloud:
qlty coverage publish cobertura.xml

See Also