Changelog - March 2025

Code coverate tags (beta)

March 30, 2025

Qlty Cloud now offers support for Coverage Tags in beta. Coverage Tags are a powerful feature that allow you to group, upload, and report on coverage data with more granularity.

Coverage Tags are particularly useful to track coverage by suite independently. For example, you can track unit test coverage separately from integration test coverage. They can also be used in monorepos to make it easy to upload and report on coverage by service.

In addition to providing clear, independent reporting of coverage metrics, Coverage Tags also allow you to carry forward coverage data from previous runs. This means that you can maintain a complete picture of your code coverage over time, even if you only run a subset of all of your tests on each commit.

To use Coverage Tags, you can add the --tag flag to the qlty coverage publish command. For example:

$
qlty coverage publish --tag unit coverage/unit.lcov
>
qlty coverage publish --tag integration coverage/integration.lcov

php-cs-fixer plugin plugin

March 27, 2025

We’ve added support for php-cs-fixer, a tool that fixes your PHP code to follow standards including the PHP coding standards as defined in the PSR-1, PSR-2, etc., or other community driven standards from organizations like Symfony.

$
qlty plugins enable php-cs-fixer

Checkstyle plugin

March 13, 2025

Qlty now supports Checkstyle, a tool that helps programmers write Java code that adheres to a coding standard.

$
qlty plugins enable checkstyle

Improved coverage comments

March 1, 2025

We’ve made significant improvements to the code coverage summary comments from Qlty Could. The new comments include more information about the coverage impact of your pull request, including diff coverage and a breakdown of coverage changes by file.

We’ve also added a “Help” section with definitions for the coverage metrics to help make it easier to interpret the results.