Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Want coverage for Windows pipeline #1064

Open
gdamore opened this issue Dec 28, 2019 · 3 comments
Open

Want coverage for Windows pipeline #1064

gdamore opened this issue Dec 28, 2019 · 3 comments

Comments

@gdamore
Copy link
Contributor

gdamore commented Dec 28, 2019

The Windows code in theory can work with CLang, which includes a bunch of features including coverage analysis. However, figuring out how to make use of this in the GitHub environment is somewhat challenging.

In addition to the challenge of collecting the data, we might have to deal with differences in the path names (slash vs backslash).

If anyone brilliant is looking at this and has already done this, I'd be grateful for a contribution.

gdamore added a commit that referenced this issue Dec 29, 2019
fixes #1063 Include sanitizer runs in CI
fixes #1068 Wssfile test sometimes fails with wrong error code

While here, addressed a number of clang-tidy items, and some light
cleanup of code we were already in.
@gdamore gdamore reopened this Dec 30, 2019
@gdamore
Copy link
Contributor Author

gdamore commented Dec 30, 2019

Accidentally closed when 1067 should have been closed.

@mauve
Copy link

mauve commented Jan 23, 2021

We have been using opencppcoverage for Code Coverage analysis on windows, very easy to setup and use, just run any (debug compiled) .exe with opencppcoverage and it will spit out coverage data.

OpenCppCoverage.exe --sources C:\PathToMySourceDir\ -- YourProgram.exe arg1 arg2

@gdamore
Copy link
Contributor Author

gdamore commented Jan 25, 2021

Thanks for the link!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants