Frequently asked questions

Twenty-five: LCOV, llvm-cov JSON, Cobertura, JaCoCo, Istanbul/nyc, SimpleCov, Clover, OpenCover, coverage.py JSON, gcov/gcovr JSON, Go coverage profiles, Coveralls JSON, SonarQube generic coverage, GNATcoverage XML, BullseyeCoverage, Visual Studio .coveragexml, Xcode’s xccov JSON, gcov’s plain-text listings, VectorCAST, Testwell CTC++, Lauterbach TRACE32, EMMA XML, UCIS/UCDB for VHDL and Verilog, NCover and dotCover DetailedXML. PIT and Stryker mutation reports load the same way and put a mutation score beside the coverage. The format is detected from the file itself, not its name, several runs merge deterministically, and any of them may arrive gzipped. Copy-paste recipes per language are on the Coverage Recipes page.

Yes. Coverage Studio for Visual Studio is a second extension with the same reader inside, for Visual Studio 2022 and 2026 — Community, Professional and Enterprise. It does not use Visual Studio's own code coverage, which in Visual Studio 2022 is an Enterprise feature: on Community and Professional it is the only coverage the IDE will show, and on every edition it reads what your build wrote — lcov, llvm-cov, gcov, Cobertura, OpenCover, Microsoft.CodeCoverage.Console's XML and the rest — rather than needing an instrumented run from Test Explorer. It reads your .vscode/settings.json too, so a repository set up for one editor is set up for both. It is included with every paid plan; a device with both editors is one seat. The user guide says where the two differ.

No, and not for lack of trying: CODESYS's own Profiler cannot say which statements ran, only how much time a POU spent — it is a profiler, not a coverage tool. Its counters live in the runtime's RAM and clear on a warm reset, with no export this extension could read even if they held the right data, and the whole thing has to be operated by hand in the IDE, which rules out running it from CI. If your PLC toolchain is Siemens instead, TIA Portal at least exports something usable.

Because Xcode’s xccov report carries no per-line data. It says how many of a file’s lines are executable and how many were covered — not which ones. Inventing gutters from that would paint confident hit counts onto blank lines, and you could not tell an invented gutter from a measured one, so they stay empty and you get file percentages, per-function counts and CodeLens instead. For line-by-line Swift coverage, export the same build with xcrun llvm-cov export -format=lcov, or use slather.

It should — every tier reloads by itself when the tracefile changes, since 0.2026.48 (the free tier's confirmation prompt is gone). If it does not: check that watch.enabled is on and that coverageFile.paths names the file your build writes, then look in the Fucini Coverage output channel — a folder under files.watcherExclude is picked up by a two-second poll rather than at once, and the channel says so.

If you have a paid subscription, plan changes, payment method and invoices are all self-service: the "Manage billing" link on your subscription page opens the customer portal. For a Business or Enterprise agreement, or anything arranged by hand, contact us and we'll get you sorted, usually the same day.

Cancel any time from the same place — "Manage billing" on your subscription page, no email required. Your licence keeps working until the end of the period you have already paid for; after that the extension settles back onto the free Community tier by itself. Nothing is uninstalled and no coverage data or settings are lost. If your licence was issued by hand, or claimed through the free Community-unlock trade, there is no subscription to cancel — just let us know and we'll stop issuing renewals.

Community is permanently free with a light usage cap on a few features and MC/DC turned off; Pro is the same feature set fully unrestricted, one machine per key. Pro Plus, Business, and Enterprise all share a "seat pool" instead — one code covering a set number of devices, freeing up automatically after a period of inactivity. Every paid plan includes Coverage Studio for Visual Studio as well as for VS Code; Community exists in VS Code only. See the pricing page for the full breakdown.

The first time Fucini Coverage Studio is installed on a machine, it gets 14 days of the full Pro feature set, counted from that first activation — not a shared calendar deadline. The trial is once per machine: reinstalling, or opening a new VS Code profile, carries on the same 14 days rather than starting new ones. Once it runs out with no activation key, the extension doesn't lock you out: it settles into the same permanent Community tier described above.

Run the "Fucini Coverage: Unlock Full Features" command from the Command Palette. It is one consent choice and one email address, asked once. After that your install sends a usage summary each day — how often you loaded coverage, in which formats and languages, which commands you ran, your coverage percentages, and which settings you changed from their defaults. No source code and no file paths go with it. The summary itself carries an install id and the request code your key was issued against, not your address; we hold the address you gave, against that request code, so that we can tell you what your install sends and delete it when you ask. Every feature, MC/DC included, unlocks for 30 days, once per machine — an extension of the 14-day trial, not a free licence. Turn telemetry back off any time and you fall back to the standard Community set; after the 30 days that happens by itself, and nothing ever breaks. For longer, there is a 7-day pass and the plans.

Only if you explicitly opt into the telemetry-unlock trade above — and only then. A normal paid Pro/Pro Plus/Business/Enterprise license never sends your username, source, or report content, regardless of what your local telemetry settings are set to; that data path is only reachable through the Community trade.

Pro Plus, Business, and Enterprise plans share one code across a fixed number of devices ("seats") instead of issuing one key per machine. The activation form calls it a subscription code on Pro and Pro Plus — buying either as one person gives you a code from your own subscription, with no company behind it — and a company code on Business and Enterprise, where a team genuinely does share one. It is the same thing either way. A seat is a device, not an editor: VS Code and Visual Studio on the same machine share one seat. A seat that's been inactive for a while frees up automatically for the next person who needs it — no admin step required for the common case.

The pool's manager (whoever's email was given when the pool was set up) gets their own login — log in and you'll land on your pool's page automatically: who's using each seat, when they were last active, and a button to free one up immediately, no need to wait for the automatic inactivity timeout or contact us.

You earn 20% of what anyone you refer pays, for their first 12 months. Full worked examples (individual and team referrals) are on the referral page.