Our current code coverage solution (cpp-coveralls) has minor differences from the code coverage results generated from an lcov file. Initial analysis shows that the lcov file is likely more correct.
Switching from cpp-coveralls to an lcov file will also be beneficial if/when we need to transition from Travis CI to another continuous integration platform.
See this comment in Issue #299 for more details.
Our current code coverage solution (cpp-coveralls) has minor differences from the code coverage results generated from an lcov file. Initial analysis shows that the lcov file is likely more correct.
Switching from cpp-coveralls to an lcov file will also be beneficial if/when we need to transition from Travis CI to another continuous integration platform.