You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying out Coverlet but unfortunately it does not seem suitable for CI/CD pipelines because it puts the generated HTML report, SVG badges etc. in a directory that is a randomly named GUID. This means that, among other things, I cannot make a repositories README file display the badges showing the coverage values as the path will be unpredictable.
The text was updated successfully, but these errors were encountered:
This is not something that Coverlet can control, unfortunately, but an issue with the underlying vstest platform. #500 discusses this extensively, and the issue is reported at microsoft/vstest#2378
The best way is to look at coverlet as a part of a toolchain, where it produces the underlying report files, which is then used to generate badges, HTML reports etc with a dedicated tool such as https://github.com/danielpalme/ReportGenerator
A CI/CD pipeline can combine the tools in a script, or as separate build steps.
@Malivil: That option unfortunately only works for the msbuild driver, not for the vstest driver. The vstest driver is recommended to use over the msbuild driver, since the latter have an architectural restriction that means it may not always reliably collect all the coverage data for larger projects or in CI environments.
I am trying out Coverlet but unfortunately it does not seem suitable for CI/CD pipelines because it puts the generated HTML report, SVG badges etc. in a directory that is a randomly named GUID. This means that, among other things, I cannot make a repositories README file display the badges showing the coverage values as the path will be unpredictable.
The text was updated successfully, but these errors were encountered: