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

UnitTest Code Coverage #260

Open
TheBlackRiderGBird opened this issue Nov 1, 2020 · 1 comment
Open

UnitTest Code Coverage #260

TheBlackRiderGBird opened this issue Nov 1, 2020 · 1 comment

Comments

@TheBlackRiderGBird
Copy link
Contributor

TheBlackRiderGBird commented Nov 1, 2020

Hi all,
I really like the unittest approach with doctest in the newest commits.
Does is make sense to have some coverage measurement established to determine how many unittests are missing.
Or do you think this goes over the top?

I already poked arround to add gcov with lcov but wasn't 100% succesful.

@centic9
Copy link
Contributor

centic9 commented Nov 2, 2020

Interesting thought!

I'm not planning to invest much time myself in having full coverage, but the tests were very helpful in narrowing down memory leaks/corruptions in combination with valgrind, so expanding them some more would be nice as they surely help to improve quality of the application overall.

Also I'd be interested in general how one can measure coverage of C++ code, so if you are able to come up with something that works, I surely will take a look and try to include it.

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

No branches or pull requests

2 participants