I think it could be useful to run code coverage on this repository, to figure out where tests can be improved :)
@KokaKiwi would have to register on codecov.io or coveralls and the ci would run over the entire repository and list some places, that the tests do not cover. Sometimes it has some mismatches, but it works most of the time.
The only thing I would change is to add an --ignore-panics flag, maybe you could also add caching to improve compilation speed? (the linked .travis.yml has it too).
I would not run this on every target and only on a single one (stable or nightly, but when you want to include doc examples in the coverage, you have to use nightly)
I think it could be useful to run code coverage on this repository, to figure out where tests can be improved :)
@KokaKiwi would have to register on codecov.io or coveralls and the ci would run over the entire repository and list some places, that the tests do not cover. Sometimes it has some mismatches, but it works most of the time.
I would recommend to use https://codecov.io/ in combination with
cargo tarpaulin(tarpaulin is way better, than kcov)For reference, you can look at this repository https://github.com/sile/hls_m3u8 and this is the
.travis.ymlhttps://github.com/sile/hls_m3u8/blob/master/.travis.ymlThe only thing I would change is to add an
--ignore-panicsflag, maybe you could also add caching to improve compilation speed? (the linked .travis.yml has it too). I would not run this on every target and only on a single one (stableornightly, but when you want to include doc examples in the coverage, you have to use nightly)