It reads the settings file the Visual Studio edition reads, fucini-coverage.json, with the keys of the VS Code settings, so a team sets its thresholds once and every edition and every pipeline judges by them. Every command documents itself: fucini-coverage help check. It is free, and it ships with 2.2026.0 build 1 of both editions — see fucini-coverage on npm and the download page.

Screenshot pending — add assets/img/cli-demo.gif (see SCREENSHOTS.md).

Both editions now carry the same version, and with it everything since 1.2026.7: a line that a failing test ran is marked, Run Tests Affected by My Changes… runs only the tests a change touches, a gate on new code stands beside the gates on the whole run, exclusions can say why, Show Minimal Test Set… finds the fewest tests that still run every line, GCC 14's condition coverage is shown line by line, Run This Test with Coverage reads Go and Rust, new code can be counted by author and by date, a CI artifact that is a zip is opened, Run App with Coverage… measures what a person reaches, and Run Mutation Tests Here asks whether a test would notice. A .NET report now shows its branch coverage, which Coverlet's spelling had hidden: those numbers move. In Visual Studio a subscription's plan now decides what it decides in VS Code. Every step is in the changelog, and both builds are on the download page.

Among the fixes: a test run's report no longer carries your user and machine name, a header of macros no longer shows as a file at 100%, an MC/DC build's branch figure matches llvm-cov report, and five report formats that were refused as unsupported are recognised. Everything is in the changelog, and both builds are on the download page.

Two reports were refused as unsupported and are read again: an llvm-cov JSON export whose first file record was long enough to push everything recognisable past the inspected head, and a gcov --json-format file of a dozen functions, which lists them before its lines. Everything is in the changelog, and both builds are on the download page.

Both editions also paint covered lines green in a new red-amber-green gutter mode, let you set the heatmap's shades with a live preview, and put the same number on the status bar as on the card it opens. Everything is in the changelog, and both builds are on the download page.

VS Code 1.2026.3 brings the two things new in both editions — risk hotspots under the tree, the functions where complex code meets little coverage, and a filter beside the sort for the files with gaps, the untested ones or those changed since the last run — and three for .NET: dotnet test without a Coverlet package, generated and designer files left out of every total, and a failed run that keeps the last good coverage on screen. Both are on the download page.

Updated 3 October: it will be free — the whole extension, on Azure DevOps Services and on Azure DevOps Server, and there will be no paid edition. Announced, not released — subscribe above to hear when it ships.

With it, VS Code 1.2026.2: the same six steps as a walkthrough on the Welcome page, and the install id left where the Visual Studio edition reads it, so one activation covers both. And a change to the terms: a refund now ends the subscription it paid for at once, one refund per customer — the refund policy has the details.

Announced, not released: it is being tested on both versions of Visual Studio before it is offered for download. Subscribe above to hear when it ships.

Each has a page with what it is, what it runs on and — for FuciniLog — the standards it adopts and what is open source. If one of these would decide something for you, say so through the contact page; that is how the order gets decided. Subscribe above to hear when each one ships.

Then the tools safety teams own: GNATcoverage XML brings Ada in at last, BullseyeCoverage and Visual Studio .coveragexml cover the commercial C/C++ and .NET toolchains, and SonarQube generic coverage is the escape hatch for anything else. Swift and Objective-C arrive through Xcode’s own xccov report — percentages and per-function counts, but no per-line data, so gutters stay empty there by design.

Coveralls JSON rounds it off, any supported format may now arrive gzipped, and copy-paste recipes per language are on the Coverage Recipes page.

Want everything unlocked, MC/DC included, without paying? Run "Fucini Coverage: Unlock Full Features" from the Command Palette and trade detailed usage telemetry for a full, unrestricted grant — reversible any time.

Community is also now its own dedicated, permanently-free listing — see the download page to grab it directly.

See the full plan breakdown on the pricing page.