From 986fa89e283b8e8a7e094eaf0d9af28fcdd0fb75 Mon Sep 17 00:00:00 2001 From: Simon B Date: Mon, 21 Jan 2019 15:01:54 +0100 Subject: [PATCH] add link to Code coverage metrics wiki page --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ae4b19c98..62a6d8d5e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,6 +34,8 @@ The most important thing you can do alongside - or even before - changing code, After that, if you want to raise code quality another level, you can use `cargo check`, `cargo cov test` and `cargo tarpaulin`. Install them with `cargo install cargo-check cargo-cov; RUSTFLAGS="--cfg procmacro2_semver_exempt" cargo install cargo-tarpaulin`. Run with `cargo cov test` and `cargo tarpaulin`. The quality check tools are often integrated with `rustc` and as a side-effect only activated when some code is compiled. Because of this, if you want a complete check you'll need to `cargo clean` first. +We have some details on [code coverage and historical numbers on the wiki](https://github.com/mimblewimble/docs/wiki/Code-coverage-and-metrics). + # Pull-Request Title Prefix **Note**: *[draft part! to be reviewed and discussed]*