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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: