stratis-storage / project

A holding place for issues that affect more than one repository in the project
4 stars 0 forks source link

Checking coverage of unit tests #15

Closed mulkieran closed 3 years ago

mulkieran commented 7 years ago

We should sometime figure out how to do this; the only recommeded way seems to be using kcov.

mulkieran commented 5 years ago

Somebody is getting code coverage info on their Rust project: https://codecov.io/gh/sagiegurari/cargo-make. Maybe this has gotten easier and we will be able to do it.

mulkieran commented 5 years ago

@waltdisgrace Could you add some notes in here indicating what you've found out so far?

waltdisgrace commented 5 years ago

Possibilities:

mulkieran commented 5 years ago

This is interesting. We could settle for a coverage report that only runs on Travis as a first step, so maybe cargo-travis is a good thing to look into first.

mulkieran commented 3 years ago

We will try with devicemapper and cargo-tarpaulin.

mulkieran commented 3 years ago

This is a start! We can close and resume again when we've learned a little more or cargo-tarpaulin becomes more flexible/expressive. It's not surprising that nothing is as advanced as the Python coverage tool yet, but it is a start.