The project's code coverage is not very high

[dota17]

Recently, I found that the project's code coverage is not very high. So I plan to improve it by adding some test cases. @baylesj
Here are results from LCOV tool:

[baylesj]

This is definitely good to know, and that's pretty abysmal for a library like us. I'd love to figure out how to get this as part of TravisCI for each patch, definitely want to get these numbers up.

[dota17]

As we know, there are two popular tools in github, which are Codecov and Coveralls. Recently, I have tested these two kind of tools, then I personally prefer to use the coveralls tool, becase it is more easy to configure, and its result is more compact, so I submit a PR about Coveralls.

Here is the PR #1061 test result,

[dota17]

Well, the result did not proceed as expected, the CI build does triggle the Coveralls, and the coverage report has been sent to the back-end, but it doesn't leave a comments .
I will keep track of this issue.

[dota17]

It seems that we should turn on the Build pushed branches button in the Travis CI's settings, because if we want to get the coverage change report, first, we should build pushed branch(usually, it's master branch), and then build pushed pull requests. Finally, the Coveralls can caculate the coverage is increased or decreased by comparing this two build result.

Furthermore, we should specify the build branches in .travis.yml :

branches:
  only:
  - master

@baylesj Please take a look. Can we turn on this button? Seems that it used to be turned on, I don't know why it's turned off now.

[baylesj]

I think it's fine to try building pushed branches. We can see if it becomes a problem.

[dota17]

Have turned it on, and it works! see the PR #1071.