Support for code coverage through -Z instrument-coverage

[ririsoft]

Hello,

Since source based code coverage is available in nightly , would that make sense to have support for dumping and showing coverage results at IDE level with rust-analyser ?

This is also mentioned in #8420 but the purpose of this feature request is to specifically focus on code coverage computation and rendering in the IDE with gutters and so independently from live/incremental testing.

For VSCode the MVP for me would be a Coverage lens that would run a given test and show related code coverage highlighting uncovered lines with a color (red by default).

Does that makes sens ?

[eggyal]

Is it independent from live/incremental testing, though? Making use of -Z instrument-coverage would require re-running affected tests in order to obtain updated coverage output.

[appaquet]

For those looking for a good alternative in VSCode for now is to use cargo-llvm-cov with the coverage gutters extension.

It is as simple as running cargo llvm-cov --workspace --lcov --output-path lcov.info and then clicking on the Watch status bar button that the extension adds. This automatically loads the new coverage data when it gets run.

[HKalbasi]

Blocked on microsoft/vscode#123713 ?

Is it independent from live/incremental testing, though? Making use of -Z instrument-coverage would require re-running affected tests in order to obtain updated coverage output.

Retesting can be invoked by a command.

[connor4312]

Blocked on microsoft/vscode#123713 ?

Test coverage has been finalized in the upcoming (1.88) release of VS Code